Attio MCP

Search and update Attio records, lists, notes and tasks, and read calls and emails

Attio is a CRM built around custom objects and lists. Its official MCP server runs at https://mcp.attio.com/mcp and has 42 tools: records, lists, notes, tasks, comments, meetings, call recordings, emails and reports. You sign in with your Attio account over OAuth, and the agent sees what your Attio user sees. The MCP server is included on every Attio plan, Free included. There is also a community server, kesslerio/attio-mcp-server, that runs locally with an API key.

Use it two ways. In Claude Code or claude.ai, your team asks about the pipeline, logs notes after calls and creates follow-up tasks without opening Attio. In your own product, each customer connects their Attio workspace over OAuth, and your agent gets the same hosted URL with that customer's token. It can log call notes on the right company, move the deal to the next stage and add a task for the rep. If your customers use HubSpot instead, the same pattern works with HubSpot.

Watch out

Writes change real records. Read tools run without confirmation and write tools ask first, so in your product keep a human approval step on update-record, merge-records and delete-task.

Limits are per workspace: 25 writes per second, 300 searches per minute and 2 semantic searches per second. Batch-heavy agents will hit them.

query-particle-sql isn't available on every plan, and notes, emails and call transcripts can carry instructions aimed at your agent. Don't let one session read them and write freely.

Install

In Claude Code:

Terminal

Loading editor...

claude mcp add --transport http attio https://mcp.attio.com/mcp

Run /mcp and sign in to Attio in the browser. In claude.ai, add Attio from Settings → Connectors. No API key is needed.

In your product, attach https://mcp.attio.com/mcp with the customer's OAuth access token as the authorization_token in the Claude API's mcp_servers, or as an Authorization: Bearer header in the AI SDK. Attio publishes standard MCP OAuth metadata: authorization code flow with PKCE, dynamic client registration at https://app.attio.com/oauth/register, and scopes mcp and offline_access for refresh tokens. The hosted server doesn't document workspace API keys. For a server-side job with an API key, run the community attio-mcp package yourself or call the Attio REST API.

More in Top MCP servers for marketing and SEO.