How do you keep Attio up to date with AI assistants?

What does the Attio MCP server let the assistants do

The Attio MCP server lets the Pebbles Ai assistants use the tools Attio itself publishes, from inside an ordinary assistant chat. Pebbles Ai acts only as an MCP client here: it calls Attio's server with the access your Attio sign-in grants and shows you what came back.

That has two consequences worth knowing before you start. Nothing syncs your Attio workspace into Pebbles Ai, so the assistant goes to Attio's server whenever it needs a record. And the set of tools is Attio's to define, so when Attio adds or changes a tool on its server, what the assistant can do changes with it.

How do you update Attio from chat

You update Attio from chat by saying what changed in plain words and letting the assistant turn it into a record change, which you approve in Manual mode. Attio lets each team shape its own data model, so name the object and attribute you mean, such as the company record or a custom stage field, rather than assuming the assistant knows your setup.

The useful moments are the ones where facts already sit in the conversation: just after a research request, after you paste notes from a meeting, or when you are about to write to an account and want to see what Attio already holds. The requests below are illustrative; what works depends on the tools Attio's server offers.

• Look up this company in Attio and tell me which attributes are empty.
• Create a company record in Attio for the firm we just researched, with its website and headcount band.
• Update the person record for the buyer we met today with her new job title.
• Before I draft this email, read what Attio holds on the account and its open deal.

How do approvals work when an assistant writes to Attio

Every call to Attio's server is an approval action, and your execution mode decides what happens to it. The web app starts in Manual, where each call, a lookup as much as a write, shows an approval card before it runs.

In Plan mode the calls are queued rather than run, which suits a long request where you want to see the whole set of changes first. In Auto they run without asking, so switch to Auto only once you trust how the assistant reads your attribute names. In Manual mode, the approval card is where you catch a wrong record or a value in the wrong field.

What the Attio integration does not do

The Attio integration does not keep anything in step by itself; every change starts with a request in a chat. If nobody asks, Attio stays exactly as it was.

• No automatic, background, real-time or two-way sync, and no field mapping between Attio and Pebbles Ai.
• Records in the Pebbles Ai CRM (in Beta) do not mirror Attio records, or the other way round.
• No connecting from chat: Attio is added in Settings, Connections, and only from the catalogue, never by URL.
• The Guider, the in-app guide, does not use MCP servers; the Marketing and Strategy assistants do.
• Disconnect removes the stored credentials in Pebbles Ai but does not revoke the grant in Attio; revoke it in Attio as well if you want it gone there.

Should Attio or the Pebbles Ai CRM hold your records

If Attio is already your system of record, keep it and let the assistants keep it current; there is no need to move records. The Pebbles Ai CRM is labelled Beta and is where Find fresh leads lands new contacts, from Pebbles Ai's own growing B2B contact database, GDPR compliant.

A workable split for an Attio team is to prospect in Pebbles Ai, review the new contacts there, then name the people worth pursuing in a chat and ask the assistant to add them to Attio, each write an approval card in Manual mode. Attio remains the place your team reports from.