Attio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATTIO_API_KEY | Yes | Your Attio API Key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aaa-health-checkA | Returns server status without requiring any credentials. |
| search-recordsB | Universal search across all resource types (companies, people, records, tasks) |
| get-record-detailsB | Get detailed information for any record type |
| create-recordB | Create a new record of any supported type |
| update-recordB | Update an existing record of any supported type |
| delete-recordB | Delete a record of any supported type |
| get-attributesB | Get attributes for any resource type (companies, people, lists, records, tasks, deals, notes) |
| discover-attributesB | Discover available attributes for any resource type |
| get-detailed-infoB | Get specific types of detailed information (contact, business, social) |
| create-noteB | Create a note for any record type (companies, people, deals) |
| list-notesB | Get notes for any record type (companies, people, deals) |
| advanced-searchB | Advanced search with complex filtering across all resource types |
| search-by-relationshipB | Search records by their relationships to other entities |
| search-by-contentC | Search within notes, activity, and interaction content |
| search-by-timeframeB | Search records by temporal criteria (creation, modification, interaction dates) |
| batch-operationsC | Perform bulk operations (create, update, delete, get, search) |
| batch-searchB | Perform batch search operations with multiple queries in parallel |
| searchB | Search Attio data by query for OpenAI MCP clients. |
| fetchA | Retrieve the full record payload for a search result ID. |
| get-listsB | Get all CRM lists from Attio (sales pipelines, lead stages, customer segments, etc.) |
| get-record-list-membershipsA | Find all CRM lists that a specific record (company, person, etc.) belongs to |
| get-list-detailsC | Get details for a specific CRM list (pipeline stages, field configuration, etc.) |
| get-list-entriesB | Get entries for a specific CRM list (companies, people, etc. in sales pipelines) |
| filter-list-entriesC | Filter entries in a CRM list by a specific attribute (e.g., stage, status) |
| advanced-filter-list-entriesB | Filter entries in a CRM list with advanced multiple conditions (complex sales pipeline queries) |
| add-record-to-listC | Add a company or person to a CRM list (sales pipeline, lead list, etc.) |
| remove-record-from-listC | Remove a company or person from a CRM list (sales pipeline, lead list, etc.) |
| update-list-entryC | Update a list entry (e.g., change stage from 'Interested' to 'Demo Scheduling') |
| filter-list-entries-by-parentB | Filter CRM list entries based on parent record properties (find companies by industry, people by role, etc.) |
| filter-list-entries-by-parent-idA | Filter CRM list entries by parent record ID (find all lists containing a specific company or person) |
| list-workspace-membersB | List all workspace members for task assignment |
| search-workspace-membersC | Search workspace members by name, email, or role |
| get-workspace-memberC | Get details of a specific workspace member |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Create a new person | Create a new person record in Attio with the provided details |
| Find a person by email | Search for a person in Attio using their email address |
| Update person details | Update an existing person record in Attio |
| Add a note to a person | Add a note to an existing person record in Attio |
| Create a new company | Create a new company record in Attio with the provided details |
| Find a company by name | Search for a company in Attio using its name |
| Update company details | Update an existing company record in Attio |
| Add a note to a company | Add a note to an existing company record in Attio |
| Search for deals | Search for deals in Attio by name or other criteria |
| Get deal details | Retrieve detailed information about a specific deal |
| Create a new deal | Create a new deal record in Attio |
| Update a deal | Update an existing deal record in Attio |
| Add a note to a deal | Add a note to an existing deal record in Attio |
| Create a new list | Create a new list in Attio for a specific object type |
| Add a record to a list | Add an existing record to a list in Attio |
| Remove a record from a list | Remove a record from a list in Attio |
| Check if a record is in a list | Check if a specific record is present in a list |
| Get entries in a list | Retrieve all entries in a specific list |
| Create a new note | Create a new note for a person or company in Attio |
| Get notes for a record | Retrieve all notes for a specific person or company |
| Update a note | Update an existing note in Attio |
| Delete a note | Delete an existing note in Attio |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
The tool set has clear distinctions in many areas, such as create/update/delete operations, but there is significant overlap among search and filter tools (e.g., advanced-search, search, search-records, filter-list-entries, advanced-filter-list-entries) that could confuse an agent about which to use for specific queries. Descriptions help differentiate some, but the boundaries are not always sharp.
Most tools follow a consistent verb-noun or verb-noun-phrase pattern (e.g., create-record, update-list-entry, get-lists), with clear and readable naming. Minor deviations exist, such as 'aaa-health-check' starting with 'aaa' and 'fetch' being a single verb, but overall the naming is predictable and well-structured.
With 33 tools, the count is borderline high for a CRM server, as it may feel heavy and overwhelming for agents to navigate. While the domain is broad, many tools could potentially be consolidated (e.g., multiple search variants), making the set less streamlined than ideal for efficient use.
The tool surface provides comprehensive coverage for CRM operations, including full CRUD for records and lists, advanced filtering, searching across various dimensions, batch operations, and management of notes and workspace members. There are no obvious gaps, and agents can handle complete workflows without dead ends.