Connect MCP clients

Use the production MCP URL unless your administrator gave you a different deployment:

OAuth discovery and consent run on https://auth.loftlancer.com. Local development defaults: MCP http://localhost:3004/api/mcp, auth http://localhost:3000 (pnpm dev:mcp / pnpm dev:auth with PLATFORM_AUTH_ENABLE_MCP=1).

After saving config, restart the client if required, then complete OAuth or device code sign-in when prompted (see Using MCP).

CursorCopy Anchor Link

1. Open Cursor Settings → MCP (or edit your MCP config file).
2. Add a remote HTTP server pointing at the endpoint above.
3. On first use, approve scopes on the auth Authorize application screen.

{
  "mcpServers": {
    "loftlancer": {
      "url": "https://loftlancer.com/api/mcp"
    }
  }
}

Replace the URL with https://collidr-mcp.vercel.app/api/mcp if your environment uses a custom NEXT_PUBLIC_MCP_URL.

Claude DesktopCopy Anchor Link

Edit claude_desktop_config.json (location depends on OS — see Anthropic docs). Add:

{
  "mcpServers": {
    "loftlancer": {
      "url": "https://loftlancer.com/api/mcp"
    }
  }
}

Restart Claude Desktop and complete browser OAuth when the Collidr tools are first used.

Claude Code (CLI)Copy Anchor Link

Claude Code supports remote MCP servers with OAuth. Configure the same HTTP URL as above in your project's MCP settings or CLI config per Anthropic's Claude Code MCP documentation.

When the CLI prints a device code, open the auth app Device sign-in page (/device on https://auth.loftlancer.com), sign in if needed, enter the code, and approve on Approve device.

VS Code / GitHub CopilotCopy Anchor Link

VS Code MCP uses mcp.json (user or workspace). Add an HTTP server entry:

{
  "servers": {
    "loftlancer": {
      "type": "http",
      "url": "https://loftlancer.com/api/mcp"
    }
  }
}

Exact schema may vary by VS Code version; use the HTTP / remote MCP option and paste https://collidr-mcp.vercel.app/api/mcp when the UI asks for a server URL. Sign in through the embedded or system browser when prompted.

WindsurfCopy Anchor Link

In Windsurf MCP settings, add a remote server with URL https://collidr-mcp.vercel.app/api/mcp. Windsurf uses OAuth-capable MCP clients similar to Cursor; follow the browser consent flow on https://auth.loftlancer.com.

Generic / custom clientsCopy Anchor Link

Collidr implements MCP over HTTP (POST /api/mcp, protocol mcp-2026-07-28 per apps/mcp GET /api/mcp discovery).

Unauthenticated POST requests receive 401 with a JSON-RPC body and WWW-Authenticate challenge (createMcpProtectedRequestHandler).

Dynamic client registration is enabled on the auth app (allowDynamicClientRegistration: true); clients may also use CIMD (mcp-2026-07-28 metadata profile) per create-platform-auth.ts.

Verify the connectionCopy Anchor Link

1. Call tool permissions_snapshot with an empty object {} — should return JSON listing tools and scopes.
2. Call organization_list — should return organizations you belong to.

If either fails, see Troubleshooting.