Server Details
Automate Attio CRM workflows with fast search and bulk operations across companies, people, deals,…
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
29 toolsaaa-health-checkTry in Inspector
Returns server status without requiring any credentials.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
add-record-to-listTry in Inspector
Add a company or person to a CRM list (sales pipeline, lead list, etc.)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | ID of the list to add the record to | |
| recordId | Yes | ID of the record to add to the list | |
| objectType | Yes | Type of record (e.g., "companies", "people") | |
| initialValues | No | Initial values for the list entry (e.g., {"stage": "Prospect"}) |
advanced-filter-list-entriesTry in Inspector
Filter entries in a CRM list with advanced multiple conditions (complex sales pipeline queries)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of entries to fetch (default: 20) | |
| listId | Yes | ID of the list to filter entries from | |
| offset | No | Number of entries to skip for pagination (default: 0) | |
| filters | Yes | Advanced filter configuration |
advanced-searchTry in Inspector
Advanced search with complex filtering across all resource types
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| query | No | Search query string | |
| offset | No | Number of results to skip for pagination | |
| filters | No | Complex filter conditions with nested array structure. Required format: { "filters": [ { "attribute": {"slug": "field_name"}, "condition": "operator", "value": "search_value" } ] } Examples: - Single filter: {"filters": [{"attribute": {"slug": "name"}, "condition": "contains", "value": "Tech"}]} - Multiple filters: {"filters": [{"attribute": {"slug": "name"}, "condition": "contains", "value": "Tech"}, {"attribute": {"slug": "categories"}, "condition": "equals", "value": "Technology"}]} - OR logic: {"filters": [...], "matchAny": true} Supported conditions: contains, equals, starts_with, ends_with, greater_than, less_than, is_empty, is_not_empty | |
| sort_by | No | Field to sort results by | |
| sort_order | No | Sort order | asc |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) |
batch-operationsTry in Inspector
Perform bulk operations (create, update, delete, get, search)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| offset | No | Number of results to skip for pagination | |
| records | No | Record data for create/update (legacy format) | |
| operations | No | Array of operations to perform | |
| record_ids | No | Record IDs for delete/get (legacy format) | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) | |
| operation_type | No | Batch operation type (legacy format) |
batch-searchTry in Inspector
Perform batch search operations with multiple queries in parallel
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results per query (default: 20) | |
| offset | No | Number of results to skip per query (default: 0) | |
| queries | Yes | Array of search query strings | |
| resource_type | Yes | Resource type to search (companies, people, records, tasks, deals) |
create-noteTry in Inspector
Create a note for any record type (companies, people, deals)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Title of the note | |
| content | Yes | Content of the note | |
| record_id | Yes | ID of the record to attach the note to | |
| resource_type | Yes | Target resource type |
create-recordTry in Inspector
Create a new record of any supported type
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| record_data | Yes | Data to create | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) | |
| return_details | No | Return full details |
delete-recordTry in Inspector
Delete a record of any supported type
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| record_id | Yes | Record ID to delete | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) |
discover-attributesTry in Inspector
Discover available attributes for any resource type
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| categories | No | Attribute categories | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) |
filter-list-entriesTry in Inspector
Filter entries in a CRM list by a specific attribute (e.g., stage, status)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of entries to fetch (default: 20) | |
| value | Yes | Value to filter by (type depends on the attribute) | |
| listId | Yes | ID of the list to filter entries from | |
| offset | No | Number of entries to skip for pagination (default: 0) | |
| condition | Yes | Filter condition (e.g., 'equals', 'contains', 'greater_than') | |
| attributeSlug | Yes | Slug of the attribute to filter by (e.g., 'stage', 'status') |
filter-list-entries-by-parentTry in Inspector
Filter CRM list entries based on parent record properties (find companies by industry, people by role, etc.)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of entries to fetch (default: 20) | |
| value | Yes | Value to filter by (type depends on the attribute) | |
| listId | Yes | ID of the list to filter entries from | |
| offset | No | Number of entries to skip for pagination (default: 0) | |
| condition | Yes | Filter condition (e.g., "equals", "contains", "starts_with") | |
| parentObjectType | Yes | Type of the parent record (e.g., "companies", "people") | |
| parentAttributeSlug | Yes | Attribute of the parent record to filter by (e.g., "name", "email_addresses", "categories") |
filter-list-entries-by-parent-idTry in Inspector
Filter CRM list entries by parent record ID (find all lists containing a specific company or person)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of entries to fetch (default: 20) | |
| listId | Yes | ID of the list to filter entries from | |
| offset | No | Number of entries to skip for pagination (default: 0) | |
| recordId | Yes | ID of the parent record to filter by |
get-attributesTry in Inspector
Get attributes for any resource type (companies, people, lists, records, tasks, deals, notes)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | Specific attribute field names | |
| record_id | No | Record ID to get attributes for (optional) | |
| categories | No | Attribute categories | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) |
get-detailed-infoTry in Inspector
Get specific types of detailed information (contact, business, social)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| record_id | Yes | Unique identifier of the record | |
| resource_type | Yes | Type of resource |
get-list-detailsTry in Inspector
Get details for a specific CRM list (pipeline stages, field configuration, etc.)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | ID of the list to get details for |
get-list-entriesTry in Inspector
Get entries for a specific CRM list (companies, people, etc. in sales pipelines)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of entries to fetch (default: 20) | |
| listId | Yes | ID of the list to get entries for | |
| offset | No | Number of entries to skip for pagination (default: 0) |
get-listsTry in Inspector
Get all CRM lists from Attio (sales pipelines, lead stages, customer segments, etc.)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get-record-detailsTry in Inspector
Get detailed information for any record type
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | Fields to include | |
| record_id | Yes | Record ID to retrieve | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) |
get-record-list-membershipsTry in Inspector
Find all CRM lists that a specific record (company, person, etc.) belongs to
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| recordId | Yes | ID of the record to find in lists | |
| batchSize | No | Number of lists to process in parallel (1-20, default: 5) | |
| objectType | No | Type of record (e.g., "companies", "people") | |
| includeEntryValues | No | Whether to include entry values in the response (e.g., stage, status) |
health-checkTry in Inspector
Returns server status without requiring any credentials.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list-notesTry in Inspector
Get notes for any record type (companies, people, deals)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| offset | No | Number of results to skip for pagination | |
| record_id | No | Record ID to list notes for | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) | |
| parent_record_id | No | Alias for record_id (backward compatibility) |
remove-record-from-listTry in Inspector
Remove a company or person from a CRM list (sales pipeline, lead list, etc.)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | ID of the list to remove the record from | |
| entryId | Yes | ID of the list entry to remove |
search-by-contentTry in Inspector
Search within notes, activity, and interaction content
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| offset | No | Number of results to skip for pagination | |
| content_type | Yes | Type of content to search | |
| search_query | Yes | Query to search within content | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) |
search-by-relationshipTry in Inspector
Search records by their relationships to other entities
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| listId | No | (Optional) List ID (must be a valid UUID if provided) | |
| offset | No | Number of results to skip for pagination | |
| source_id | Yes | Source record ID | |
| relationship_type | Yes | Relationship type | |
| target_resource_type | No | Target resource type |
search-by-timeframeTry in Inspector
Search records by temporal criteria (creation, modification, interaction dates)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return | |
| offset | No | Number of results to skip for pagination | |
| end_date | No | End date (ISO 8601 format) | |
| start_date | No | Start date (ISO 8601 format) | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) | |
| timeframe_type | No | Timeframe filter type |
search-recordsTry in Inspector
Universal search across all resource types (companies, people, records, tasks)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order | |
| limit | No | Maximum number of results to return | |
| query | No | Search query string | |
| fields | No | Fields to search (content) | |
| offset | No | Number of results to skip for pagination | |
| date_to | No | End date for filtering (ISO 8601 format) | |
| filters | No | Advanced filter conditions | |
| date_from | No | Start date for filtering (ISO 8601 format) | |
| timeframe | No | Relative timeframe filter | |
| date_field | No | Which date field to filter on | created_at |
| match_type | No | String matching | |
| search_type | No | Type of search | |
| created_after | No | Filter records created after this date (ISO 8601) | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) | |
| updated_after | No | Filter records updated after this date (ISO 8601) | |
| created_before | No | Filter records created before this date (ISO 8601) | |
| updated_before | No | Filter records updated before this date (ISO 8601) |
update-list-entryTry in Inspector
Update a list entry (e.g., change stage from 'Interested' to 'Demo Scheduling')
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | ID of the list containing the entry | |
| entryId | Yes | ID of the list entry to update | |
| attributes | Yes | Attributes to update on the list entry |
update-recordTry in Inspector
Update an existing record of any supported type
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| record_id | Yes | Record ID to update | |
| record_data | Yes | Updated data | |
| resource_type | Yes | Type of resource to operate on (companies, people, lists, records, tasks) | |
| return_details | No | Return full details |
FAQ
How do I claim this server?
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}
The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
What are the benefits of claiming a server?
- Control your server's listing on Glama, including description and metadata
- Receive usage reports showing how your server is being used
- Get monitoring and health status updates for your server