Connect Attio to Claude Code

Query records, lists, notes and tasks in Attio's configurable CRM data model. Add Toolspoke to Claude Code once and it can use 13 Attio actions. Your Attio credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

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

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Attio and connect it

    Add Attio to a project in your Toolspoke workspace.

    Workspace API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Workspace API key
    Attio → Workspace settings → Developers → API keys → Create key. Tick the scopes the actions you plan to use need: record_permission for reading and writing records, object_configuration and list_configuration for the schema reads, note_permission for notes, task_permission for tasks, and user_management for the member list. The key belongs to one workspace, so a second workspace needs a second install.
  3. Choose what Claude Code may do

    All 13 actions start on. Switch off any of the 3 actions that change something in Attio, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Attio actions that only read, so they are safe to try first.

  • Query the records on one object, this is the main way to read anything out of Attio
  • Fetch one record in full, with every attribute value Attio holds for it
  • List every object this workspace defines, standard and custom, with its slug, singular and plural names and id
  • List the attributes defined on one object, with each attribute's slug, title, type and whether it is unique

What Claude Code can do in Attio

10 actions read and 3 write.

Reads

  • Query records

    Query the records on one object, this is the main way to read anything out of Attio. `object` is the object's slug or id, from list_objects: "people", "companies" and "deals" exist in most workspaces, but a workspace defines its own objects, so check rather than assume. `filter` is Attio's own filter document keyed by attribute slug, and `sorts` is a list of {"direction": "asc"|"desc", "attribute": "<slug>"} entries. Call list_attributes for the attribute slugs this workspace actually has before filtering on anything beyond the obvious ones, a filter naming an attribute that does not exist comes back as an error rather than as an empty result. Pages by offset, not by cursor.

  • Get record

    Fetch one record in full, with every attribute value Attio holds for it. Takes the object slug and the record's own id, both of which query_records returns. Use this after a query when you need the values the query did not show you.

  • List objects

    List every object this workspace defines, standard and custom, with its slug, singular and plural names and id. Call this first whenever you do not already know what the workspace calls something: Attio ships People, Companies, Deals and Users by default, and a workspace is free to add its own or rename those. The slug is what every other operation here takes as `object`.

  • List attributes

    List the attributes defined on one object, with each attribute's slug, title, type and whether it is unique. This is the translation table between what a person says and what the API takes, "the company's website" is an attribute with a slug, and query_records, create_record and update_record all speak in slugs. Call it before filtering or writing anything you have not seen this workspace return.

  • List lists

    List the workspace's lists. Attio's pipelines and saved collections, each with its slug, name, id and which object its entries point at. A list is where a workspace tracks a process (a sales pipeline, an onboarding queue), so this is the operation that finds the pipeline before list_list_entries reads what is in it.

  • List list entries

    Read the entries on one list, the records currently in that pipeline or collection, with the per-entry attribute values the list itself holds (stage, owner, dates). Takes the list slug or id from list_lists. `filter` and `sorts` have exactly the same shape as query_records, but the attribute slugs are the list's own, which list_attributes returns when asked about a list rather than an object.

  • List notes

    List notes, newest first, the written history of what people in the workspace have said about a record. Give `parent_object` and `parent_record_id` together to read one record's notes; leave both off to read the workspace's recent notes across every record, which is a much broader read and should be paged rather than pulled whole.

  • List workspace members

    List the people who have access to this Attio workspace, with each member's id, name, email address and access level. Call it to turn a colleague's name into the workspace member id that an owner or assignee attribute takes. These are the caller's own colleagues, not records about anybody the workspace sells to.

  • List tasks

    List tasks, with their text, deadline, assignees and the records they are linked to. Narrow it with `linked_object` plus `linked_record_id` to see one record's outstanding work, or with `assignee` to see one person's. `sort` takes Attio's own combined field and direction, e.g. "created_at:desc".

  • Identify

    Report what this connection's API key actually is: which workspace it belongs to, which workspace member created it, and the exact list of scopes it was granted. It needs no scope of its own, which is why it is the connection check, it answers "is this key real and whose is it" without depending on any permission the key may not have been given. Call it when a write comes back refused, to see whether the scope is missing rather than the record.

Writes

  • Create record

    Create a record on one object. `values` is a map of attribute slug to value, in Attio's own value shape, a text attribute takes a string, a multiselect takes a list, and a record-reference attribute takes a list of {"target_object", "target_record_id"}. Call list_attributes first for the slugs and types this workspace defines. Attio refuses a create that collides with a unique attribute, so query_records first when the record may already exist and use update_record when it does.

  • Update record

    Change attribute values on an existing record. Only the attributes you send are touched. This uses Attio's appending update, a value sent for a multiselect attribute is added to what is already there rather than replacing it, which is the reversible half of the two update verbs Attio offers; the overwriting one is deliberately not exposed. This cannot delete the record.

  • Create note

    Attach a note to a record. The note appears on that record's timeline inside the workspace; it is not sent to anybody outside it, which is why this is a write rather than a destructive action. Say which object the record belongs to and give its id, both come from query_records. `format` is "plaintext" or "markdown"; markdown supports headings, lists, emphasis and links, and image embeds are not accepted through the API. `created_at` back-dates the note and may not be in the future.

Attio in Claude Code: questions

Does Claude Code see my Attio credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Attio?

Yes. Each of the 13 actions can be switched off for a project. Turn off the 3 that change something and Claude Code can only read.

Will 13 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Attio action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Attio call does not run in a sandbox, so it bills nothing.

Try Attio in Claude Code

Free to start, and tool calls cost nothing on any plan.