Connect your client

Get your connect URL and add Lancer to Claude, Claude Code, ChatGPT, Codex, Cursor, and more.

Every client connects the same way: one URL, no OAuth, no extra headers. Get the URL once, then follow the section for your client below.

Get your connect URL

Open the Lancer web app and go to MCP in the sidebar. The Authentication card shows your personal connect URL; it is created automatically the first time you open the page:

https://api.lancer.app/mcp?token=lmc_XXXXXXXXXXXXXXXX_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Click Reveal to see it, then Copy. Clients that accept custom headers can also send the key as Authorization: Bearer lmc_... against the bare endpoint.

The URL is a credential

The lmc_... key grants access to every Lancer organization you belong to. Treat the full URL like a password. If it leaks, click Regenerate key on the MCP page; the old key stops working immediately.

Claude Code

Add the server from your terminal, replacing the URL with your own:

claude mcp add --transport http lancer "https://api.lancer.app/mcp?token=lmc_..."

By default this registers the server for the current project. Add --scope user to make it available in every project:

claude mcp add --transport http --scope user lancer "https://api.lancer.app/mcp?token=lmc_..."

Verify with claude mcp list, or run /mcp inside a session to see the connection status and browse tools. The set_up_lancer prompt appears as the slash command /mcp__lancer__set_up_lancer.

Claude (claude.ai and Claude Desktop)

Custom connectors require a paid Claude plan.

Go to Settings, then Connectors (on the web: claude.ai/settings/connectors; in Claude Desktop: Settings, then Connectors).

Click Add custom connector, name it Lancer, and paste your connect URL as the remote MCP server URL. Leave the OAuth fields empty; the token in the URL is the authentication.

Start a new chat, open the search-and-tools menu, and make sure the Lancer connector is enabled. Then ask something like "List my Lancer organizations" to confirm it works.

On mobile, connectors added on the web are available too, so you can manage your pipeline from your phone.

ChatGPT (chatgpt.com)

Custom MCP connectors in ChatGPT require developer mode.

Enable developer mode: Settings, then Apps and Connectors, then Advanced settings, and turn on Developer mode.

Back in Apps and Connectors, click Create (custom connector). Name it Lancer, paste your connect URL as the MCP server URL, and choose No authentication; the token travels in the URL.

In a new chat, open the plus menu, choose Developer mode, and enable the Lancer connector. ChatGPT asks for confirmation before running write tools; read the previews before approving.

Codex

The Codex CLI configures MCP servers in ~/.codex/config.toml. Recent Codex versions support remote servers over Streamable HTTP directly:

~/.codex/config.toml

[mcp_servers.lancer]
url = "https://api.lancer.app/mcp?token=lmc_..."

If your Codex version only supports stdio servers (command-based entries), bridge with mcp-remote:

~/.codex/config.toml

[mcp_servers.lancer]
command = "npx"
args = ["-y", "mcp-remote", "https://api.lancer.app/mcp?token=lmc_..."]

Restart Codex and check the server is listed with codex mcp list.

Cursor

Add this to .cursor/mcp.json in your project, or ~/.cursor/mcp.json to make it global:

.cursor/mcp.json

{
  "mcpServers": {
    "lancer": {
      "url": "https://api.lancer.app/mcp?token=lmc_..."
    }
  }
}

Then enable the server under Cursor Settings, then MCP. Tools are used by the agent automatically; writes ask for your approval.

VS Code (GitHub Copilot)

Add this to .vscode/mcp.json in your workspace:

.vscode/mcp.json

{
  "servers": {
    "lancer": {
      "type": "http",
      "url": "https://api.lancer.app/mcp?token=lmc_..."
    }
  }
}

Open Copilot Chat in agent mode and the Lancer tools appear in the tools picker.

Any other client

Two universal options, in order of preference:

Remote HTTP support. Give the client your connect URL as a Streamable HTTP MCP server. If the client configures auth separately from the URL, you can instead point it at https://api.lancer.app/mcp with header Authorization: Bearer lmc_....
stdio bridge. For clients that only launch local stdio servers, use mcp-remote as the command: npx -y mcp-remote "https://api.lancer.app/mcp?token=lmc_...".

Token semantics

A few things worth knowing about the token behind the URL:

Personal, not per-organization. The token identifies you. If you belong to several organizations, the agent picks one per call; the server re-checks your live memberships on every tool call.
One active token per user. Regenerating revokes all your previous tokens immediately.
Always available. Your connect URL can be revealed and copied again from the MCP page at any time.
POST only, stateless. The endpoint speaks Streamable HTTP without server-push sessions, which is what all the clients above expect. No configuration needed.

Verify the connection

Ask your agent something simple:

List my Lancer organizations.

The agent should call the organization_list tool and answer with your organization name(s). If it fails, check Access, limits, and errors.

On this page