Attio

Attio's data model is configured per workspace, so the objects, attributes and deal stages one workspace has are not the ones another has. The tools tell the agent to read that schema before it writes, so a custom object such as "products" is addressed by the slug the workspace defined and not by a guess. It authenticates with an Attio API key, one per workspace.

Does Attio have an MCP server?

Yes. Attio hosts its own at https://mcp.attio.com/mcp. Sign-in is OAuth with your Attio account and needs no API key, and Attio's documentation names Claude, ChatGPT and Cursor among the clients that can connect. Reads run without a prompt, writes ask for confirmation, and access follows the permissions of the signed-in user. Tulina's Attio connector is the other route: an API key held in Tulina's vault, reachable from the same MCP link as the rest of your tools.

How do you connect Attio to Claude and ChatGPT?

Through Tulina's MCP server, in three steps:

1. In your Attio workspace's developer settings, open the API section and create an access token. Tick the permissions for records, notes, tasks and lists. To let the connector add attributes, select options or deal stages, also grant object_configuration:read-write (list_configuration:read-write for a list).
2. Paste the token into Tulina's Attio connector, for yourself or for the organisation. It is stored in the vault and never shown to the model.
3. Add https://mcp.tulina.ai/mcp to Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.

A second workspace is a second named account, and a request names the one it is for. A total across several accounts is made by asking each one in turn.

Tulina vs Attio's official MCP server

Both reach the same CRM. The table covers what differs, from Attio's documentation page and from the connector's tool schemas. Tulina's own card says Attio's server is now the more complete of the two.

If Attio is the only system the model needs, or you want its reports and email history, Attio's own server is the better choice. Tulina earns its place when a CRM record is one step in a longer piece of work.

What you can ask it

"Is there already a person with this email before I add her?" The agent searches people with an email filter, because a name search does not match an address, and only creates the record when nothing comes back.

"Add a note to the Acme deal summarising today's call." The agent finds the deal, then writes a markdown note attached to it. Attio's API cannot edit a note, so a correction is a delete and a new note.

"Add a Negotiation stage to deals." The agent reads the stages that exist, then creates the missing one. Attio's API has no delete for a stage, so the connector checks first and adds only what is absent.

Attio sits at the centre of three published processes: customer call prep, lost-deal revival and deal scoring on arrival. It pairs with Granola for call notes and Linear when a request from a customer becomes an issue.

What the Attio connector can't do

• It does not read or send email, run Attio reports or run SQL. Attio's own server exposes all three.
• Meetings and call recordings are read-only, transcripts included. Attio does not expose writes on them.
• Attributes, select options and statuses can be added, and none can be deleted through the API.
• A merge is irreversible. Attio marks both records as merged and creates a third.
• A note body cannot be edited, and a task's text cannot be changed. Only its deadline, completion, assignees and linked records can.
• Listing notes returns the oldest first, ten at a time by default, with no date filter. Recent notes are at the end, so the agent scopes the call to a record when it can.
• Comments need a parent record or a list entry. Attio refuses an unfiltered listing.
• Search by name matches a substring of the name. An address or a domain needs a filter instead.
• The key sees what its permissions allow. A workspace added later needs its own key.