Attio MCP Server
Let your agent read and update Attio CRM records—contacts, companies, deals, tasks, and notes—while you run outbound, support, or founder-led sales from the terminal.
Overview
io.github.kesslerio/attio-mcp-server is a MCP server for the Grow phase that connects AI agents to Attio CRM for contacts, companies, deals, tasks, notes, and workflows.
What is this MCP server?
- Full or search-only tool modes via ATTIO_MCP_TOOL_MODE (full vs search)
- Manage contacts, companies, deals, tasks, notes, and workflows in Attio
- Requires ATTIO_API_KEY; optional ATTIO_WORKSPACE_ID for workspace-scoped ops
- npm package attio-mcp v1.6.1 with stdio transport
- Configurable MCP_LOG_LEVEL (DEBUG through ERROR)
- Server version 1.6.1; npm identifier attio-mcp
- Environment variables documented: ATTIO_API_KEY (required), ATTIO_WORKSPACE_ID, ATTIO_MCP_TOOL_MODE, MCP_LOG_LEVEL
Community signal: 68 GitHub stars.
What problem does it solve?
Founders lose hours tabbing between Attio and their coding agent when pipeline questions need live CRM data.
Who is it for?
Solo B2B builders on Attio who want Claude Code or Cursor to draft follow-ups, summarize deals, or log notes without manual copy-paste.
Skip if: Teams on HubSpot/Salesforce only, or anyone unwilling to store an Attio API key in local MCP environment variables.
What do I get? / Deliverables
After install, your agent can query and (in full mode) manage Attio objects so sales and support workflows stay in one conversational surface.
- Agent-callable Attio tools for records, deals, tasks, and notes
- Health-check path that works before API key is wired (per registry env docs)
- Operational logging via MCP_LOG_LEVEL for debugging CRM calls
Recommended MCP Servers
Journey fit
CRM access sits in Grow because solo builders use Attio to nurture leads and customers after ship; MCP bridges that lifecycle data into agent workflows without exporting CSVs. Lifecycle is the canonical shelf for CRM mutations and follow-ups—deals, tasks, and notes map to customer journey operations, not greenfield backend code.
How it compares
Attio CRM MCP bridge, not a standalone CRM product or a generic web-scraping skill.
Common Questions / FAQ
Who is io.github.kesslerio/attio-mcp-server for?
It is for indie SaaS founders and small teams using Attio who want their coding agent to read and update CRM records during sales and customer lifecycle work.
When should I use io.github.kesslerio/attio-mcp-server?
Use it when you are in active pipeline management—researching accounts, updating deals, logging call notes, or triaging tasks—and want those actions agent-driven via MCP.
How do I add io.github.kesslerio/attio-mcp-server to my agent?
Configure the npm stdio server `attio-mcp`, set ATTIO_API_KEY (required), optionally ATTIO_WORKSPACE_ID and ATTIO_MCP_TOOL_MODE, then restart your MCP client.