The Attio connector.
Records, lists, notes and tasks. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Attio exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Attio defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Attio tool
6 tools, named as the agent sees them.
- list_objectsread
List every object in the workspace (people, companies, deals, and any custom object) with its api_slug and id. Call this FIRST — query_records and get_record both need an object slug, and workspaces rename or add objects freely so the slugs cannot be assumed.
- query_recordsread
Query the records of one object — this is the main way to read CRM rows. Takes an object slug from list_objects and an optional Attio filter object (e.g. {"name":{"$contains":"Acme"}}) and sort spec. Returns record_ids for get_record. Attio implements this as a POST with a filter body; it reads only.
- get_recordread
Get one record with every attribute value. Use after query_records when you need the full row rather than the summary fields.
- list_listsread
List the workspace's lists (pipelines and saved views such as "Sales Pipeline" or "Inbound Leads") with the object each one is built on. Use to discover what pipelines the team actually runs.
- list_notesread
List notes, newest first. Pass parent_object + parent_record_id (from query_records) to read the notes on one company or person — that is the account history a rep would skim before a call.
- list_tasksread
List tasks with their content, deadline, completion state and assignees. Use to answer "what is outstanding on this account" — scope with linked_object + linked_record_id from query_records.
Use it from any agent
The same Attio tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Attio API Key in your Attio account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Attio once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.