MCP Server

The Lancer MCP server lets AI assistants create and update projects, tasks, subtasks (todos), and milestones in your Lancer account. Each connection uses a personal access token (PAT) scoped to one account — your AI tool never needs your login password.

• Account-scoped tokens — one PAT works for a single Lancer account
• 14 tools for projects, tasks, and milestones
• Works with Cursor, Claude Desktop, ChatGPT Desktop, and Kiro
• Built-in rate limits to protect your account and infrastructure

1. Sign in to Lancer at https://app.lancer.pro
2. Open Settings → Integrations → AI Tools
3. Click "Create token", choose a name and expiration, then copy the token immediately
4. Store the token securely — it is only shown once

All supported clients use the same mcpServers.lancer block. Replace lnc_pat_YOUR_TOKEN_HERE with the token you copied from Lancer.

{
  "mcpServers": {
    "lancer": {
      "command": "npx",
      "args": ["-y", "@lancerapp/mcp-server"],
      "env": {
        "LANCER_API_URL": "https://api.lancer.pro",
        "LANCER_PAT": "lnc_pat_YOUR_TOKEN_HERE"
      }
    }
  }
}

The account is inferred from your token automatically — you do not need to pass an account id in tool calls.

1. Open Cursor → Settings → MCP (or edit the config file directly)
2. Add the lancer entry under mcpServers (merge with existing servers if needed)
3. Paste your PAT and confirm LANCER_API_URL is set correctly
4. Restart Cursor or refresh the MCP panel

1. Quit Claude Desktop completely
2. Open claude_desktop_config.json (create it if missing)
3. Add the lancer entry under mcpServers and save
4. Restart Claude Desktop

ChatGPT Desktop (recommended for local MCP)

1. Edit mcp_config.json with the JSON block above
2. In recent builds: Settings → Advanced → MCP Servers
3. Restart ChatGPT Desktop

1. Open the command palette and run "Kiro: Open workspace MCP config (JSON)" (or user config)
2. Add the lancer entry under mcpServers and save
3. Confirm "lancer" appears in the MCP servers panel

Projects

Tasks

Milestones

Lancer enforces limits on PAT-authenticated requests to prevent abuse and runaway AI tool usage.

• HTTPS is required for non-local API URLs in the MCP client
• Tokens are hashed at rest and shown only once at creation
• Revoke tokens immediately if exposed
• Never commit PATs to git or share config files containing real tokens

Need help? Contact support from the Lancer app or visit the Support page on this site.