The MCP server

leadrack exposes its lead operations as a Model Context Protocol server, so connecting an AI agent to your pipeline means pasting a URL instead of writing HTTP glue. Same operations, same guardrails, same timeline attribution as the REST API. MCP is a different door into the same room.

Connecting

The server speaks streamable HTTP at:

https://app.leadrack.io/api/mcp

Auth is the same bearer key as the REST API. Examples:

Claude Code

claude mcp add --transport http leadrack \
  https://app.leadrack.io/api/mcp \
  --header "Authorization: Bearer lr_..."

Claude API (MCP connector): pass the URL in mcp_servers with your key as authorization_token, plus an mcp_toolset entry.

Anthropic Managed Agents: declare the server on the agent, and store the key in a vault as a static_bearer credential for the server URL.

Cursor and other clients: add a streamable-HTTP server with an Authorization: Bearer header.

The tools

Eleven tools mirror the API surface:

• Context: list_pipelines (pipelines, stage keys, and the custom-field schema in one call; agents should call this first), list_cards, search_contacts, get_contact, get_timeline.
• Writes: add_lead (idempotent, like the REST endpoint), update_contact (enrichment), move_card (stage keys, never UUIDs).
• Email: draft_email, send_draft_email, send_email. Sends run through your verified domain with every guardrail, and clients like Claude add their own tool-approval step on top.

Deletes and bulk import are REST-only on purpose. Destructive and batch operations belong where integrators are explicit, not one autocompleted tool call away.

Attribution and limits

MCP calls authenticate through the same per-key rate limiting as REST and land on lead timelines under the key's name. Name the key after the assistant that holds it ("claude-desktop", "sales-agent") and every board mutation stays auditable.

A note on claude.ai's web connector

The MCP server authenticates with bearer keys, which covers Claude Code, the API connector, Managed Agents, and IDE clients. claude.ai's web connector UI prefers OAuth; that's on the roadmap rather than in the product today.