Does Lasso have an MCP server?
Lasso maintains an official MCP server.
For Lasso customers only: tool calls need your Lasso license key.
- Access
- Remote server
- Endpoint
- https://lasso.link/mcp
- Category
- Marketing
A remote server run by Lasso itself — nothing to install. Documented at getlasso.co.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http lasso https://lasso.link/mcpAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://lasso.link/mcp - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"lasso": {
"url": "https://lasso.link/mcp"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"lasso": {
"type": "http",
"url": "https://lasso.link/mcp"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://lasso.link/mcp - Complete sign-in, then enable the connector in a new chat
Does Lasso have an official MCP server?
Yes. Lasso maintains an official MCP server, hosted at https://lasso.link/mcp.
How do I connect Lasso to Claude?
Add https://lasso.link/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http lasso https://lasso.link/mcp" in Claude Code.
Do I need to install anything to use the Lasso MCP server?
No. It is a remote server hosted by Lasso, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under getlasso.co's namespace co.getlasso, and getlasso.co links a 'Lasso MCP' page from its main navigation; the endpoint lasso.link/mcp answers MCP initialize as 'lasso' and asks for a license key from app.getlasso.co. GitHub metadata is refreshed every six hours.
Published to the MCP Registry under getlasso.co's namespace co.getlasso, and getlasso.co links a 'Lasso MCP' page from its main navigation; the endpoint lasso.link/mcp answers MCP initialize as 'lasso' and asks for a license key from app.getlasso.co.
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.