MCP

Connect Productlane to Claude, Cursor, VS Code, or any MCP-compatible client so an AI agent can read and act on your workspace directly. The agent can triage threads, send replies, file issues, publish changelogs, and manage docs, all within the permissions you grant.

For the complete setup reference, see the full MCP guide.

Server URL

https://productlane.com/api/mcp

One endpoint serves every client. There are two ways to authenticate, both exposing the same tools. Pick based on who is connecting.

Option 1: Connect with OAuth (recommended)

Best for connecting an AI client to your own workspace. One click in the client, no keys to copy, and you choose exactly what to grant.

1. Add the server in your client and point it at https://productlane.com/api/mcp.

   • Cursor: Settings → MCP → Add new MCP server.

   • Claude: Settings → Connectors → Add custom connector.

   • Claude Code: run claude mcp add --transport http productlane https://productlane.com/api/mcp.

   • VS Code: Command Palette → MCP: Add Server → HTTP.

2. The client opens a Productlane authorization screen in your browser.

3. Sign in if needed, pick the workspace to connect, and choose the access to grant: Full requested access, or Only select permissions to pick individual ones.

4. Click Authorize. The client is connected.

Review and revoke connected apps anytime in Settings → Integrations → API → Connected apps. Revoking stops that app's access immediately.

Option 2: Connect with an API key

Best for scripts, servers, or any setup without a browser to complete the OAuth flow.

1. Create a key in Settings → Integrations → API and pick the scopes the integration needs. Copy the key (shown once).

2. Add the server in your client, pointing it at https://productlane.com/api/mcp, and pass the key as the Authorization: Bearer pl_v2_... header.

For Claude, add it as a custom connector:

{ "mcpServers": { "productlane": { "url": "https://productlane.com/api/mcp", "headers": { "Authorization": "Bearer pl_v2_..." } } } }

For Cursor, go to Settings → MCP → Add new MCP server and use the same URL and header.

To rotate a key, create a new one, update the client config, then revoke the old key.

What the agent can do

The MCP server exposes the same surface as the v2 API. Connected clients can work with:

• Threads - list, read, update status, send messages, and post internal comments.

• Contacts and companies - look people and organizations up, create and update them, and manage blocked senders.

• Issues and projects - file issues to Linear, read workflow states, and manage projects.

• Changelogs - draft, publish, and broadcast entries, and manage changelog tags.

• Docs - create and update help center articles and groups, and propose drafts for review.

• Tags, members, and the portal - manage tags and tag groups, invite and manage members with admin, and read the public roadmap.

Each tool is gated by the scopes you grant, so the agent only sees the tools its access allows.

Example prompts

Once connected, ask the client in plain language:

• "Summarize my open threads from the last 24 hours and draft a reply to the oldest one."

• "Create a Linear issue from this thread and link it to the customer's request."

• "Find every company on the Enterprise tier with an open thread."

• "Draft a changelog entry for the project we just shipped, then leave it unpublished for review."

• "Propose a help center article explaining our new export feature, as a draft for review."

Scopes control what the agent can do

Whichever method you use, access is limited to the scopes you grant: reading and managing threads, contacts, companies, changelogs, help center articles, projects, issues, and tags, plus member and workspace management with admin. A read-only key or grant exposes only read tools. Grant a narrow set when you want the agent limited to part of your workspace.

For the full list of scopes and what each one covers, see the API article.

Verify the connection

Ask the client to call me_get. It returns your workspace, the key id, and the granted scopes. If it fails, the key or grant is missing, was revoked, or is a deprecated v1 key.

Troubleshooting

• A tool is missing. The connection lacks the scope that tool needs. Re-authorize with the OAuth flow and grant the scope, or mint a new key with it.

• 401 unauthenticated. The key or grant is missing or malformed. Reconnect the server.

• 410 unsupported_key_version. You passed a deprecated v1 key. Mint a v2 key in Settings → Integrations → API and use that.

• 429 rate_limited. You hit the rate limit. Reads allow 1000 requests per minute and writes 60 per minute, per key. The client should wait for the window in the Retry-After response header.

Revoke access

For an OAuth connection, revoke the app in Settings → Integrations → API → Connected apps. For an API key, revoke the key in Settings → Integrations → API. The client stops working immediately.