Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add attio-mcp -- npx -y attio-mcp@1.7.0Ejecútalo en una terminal.
{ "mcpServers": { "attio-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirA comprehensive Model Context Protocol (MCP) server for Attio, providing complete CRM surface coverage. This server enables AI assistants like Claude and ChatGPT to interact directly with your entire Attio workspace through natural language—manage Deals, Tasks, Lists, People, Companies, Records, and Notes without falling back to raw API calls.
Transform your CRM workflows with AI-powered automation. Instead of clicking through multiple screens, simply ask Claude or ChatGPT to find prospects, update records, manage pipelines, and analyze your data using natural language commands.
🎉 v1.0.0 Milestone: Complete Attio CRM surface coverage with full ChatGPT Developer Mode integration.
"Find all AI companies with 50+ employees that we haven't contacted in 30 days and add them to our Q1 outreach list"
⚠️ Smithery Temporarily Unavailable: Smithery has changed their deployment model to require external hosting. We're working on Cloudflare Worker hosting for ChatGPT users. In the meantime, use Tier 4 (Cloudflare Worker) for ChatGPT/remote access.
ChatGPT Pro/Plus users can access the Attio toolset through natural language using a self-hosted Cloudflare Worker:
Focused Tool Surface: Consolidated 40+ resource-specific tools into universal operations, then added scoped high-frequency write tools for safer company and deal updates.
records_search and records_search_advancedcompanies_create and companies_updaterecords_search_by_relationshiprecords_batchrecords_get_inforecords_search_by_relationshiprecords_get_interactionslist_entries_filter - Unified filtering with 4 modeslist_entries_manage - Unified entry management with 3 modeslist_entries_list - Retrieve list entriesrecords_get_list_memberships - Find record's list membershipsrecords_create/records_update reject resource_type: "lists"):
lists_create - Create lists with first-class access controls: workspace_access (full-access | read-and-write | read-only | "null" for a private list) and workspace_member_access (per-member grants). Omitting both access fields defaults the new list to workspace-wide full access; new lists must keep at least one full-access grantee.lists_update_configuration - Update name, custom fields, and the same access controls. Member-level grants can raise access above the workspace default but never lower it below workspace_access.plan_gating (workspace plan does not support the requested access configuration) from permission_failure (token/workspace permissions) and unsupported_input (malformed access config), each with a suggested next step.deals_create and deals_updateresource_type parameterSupercharge Claude's Attio knowledge with pre-built skills that prevent common errors and teach best practices.
Quick Start (solves "wrong field name" errors):
npx attio-discover generate-skill --all --zip
# Import ZIP into Claude Desktop: Settings > Skills > Install Skill
See Skills Documentation for complete setup and usage guides.
Intelligent shortcuts that help Claude work faster with your CRM data:
See Using Out-of-the-Box Prompts for detailed documentation and examples.
NEW: 10 pre-built MCP prompts for common Sales workflows. No setup required—just use them!
# Search for prospects
"Use people_search.v1: Find Account Executives in San Francisco at fintech companies, limit 25"
# Log activity
"Use log_activity.v1: Log a call with Nina at Acme Corp, discussed Q1 pricing, create follow-up task"
# Qualify a lead (with web research)
"Use qualify_lead.v1: Qualify Acme Corp using BANT framework, dry run mode"
# Meeting prep
"Use meeting_prep.v1: Prepare for meeting with contact at Acme Corp"
All read prompts support:
format: table | json | ids (default: table)fields_preset: sales_short | full (default: sales_short)verbosity: brief | normal (default: brief)All write prompts support:
dry_run: true | false (default: false) - Preview changes without executingPrompts include built-in token optimization:
MCP_DEV_META=true for token counts in responsesPROMPT_TELEMETRY_ENABLED=true for usage loggingMAX_PROMPT_TOKENS environment variableFor complete prompt documentation, see docs/prompts/v1-catalog.md.
/objects/tasks/attributes has limitations, handled with fallback patternsreadOnlyHint, destructiveHint) so OpenAI Developer Mode can auto-approve reads and request confirmation for writes.tools/list for the current inventory. Do NOT set ATTIO_MCP_TOOL_MODE in Smithery configuration for full access.search, fetch, aaa-health-check), explicitly configure ATTIO_MCP_TOOL_MODE: 'search' in Smithery dashboard when Developer Mode is unavailable.Tool selection is answerable from static metadata, so a client does not have to guess by calling things and reading the errors.
capabilities_get (full mode only) publishes the permitted capability
manifest: for every tool this server advertises, its input and output schemas
plus the operation facts — action, resource types, read-only/destructive/
idempotent flags, whether a credential is required, pagination style and cap,
and guidance on capability, boundaries, limits, and recovery.aaa-health-check returns the same manifest for its permitted set, projected
to its operation sections, so a search-only client can see what it is allowed
to use without widening its allowlist. Schema documents come from
capabilities_get or tools/list; the health payload says so in
capabilities.projection.A listed tool is configured, not granted. Authorization is still enforced on every call, so a manifest entry can still come back denied.
For detailed troubleshooting and solutions, see TROUBLESHOOTING.md and GitHub Issues.
Build powerful CRM queries with multi-criteria AND/OR filtering. See the Advanced Search Guide for complete examples and operator reference.
⚠️ IMPORTANT: Correct Package Name
The npm package name is
attio-mcp(notattio-mcp-server). The GitHub repository is namedattio-mcp-server, but the npm package was renamed toattio-mcpin June 2025. Installingattio-mcp-serverwill give you an outdated v0.0.2 release with only 4 legacy tools.
Choose your installation method:
Best for: Developers who prefer local installations with automatic configuration.
One-command scripts that install attio-mcp and configure your client automatically.
curl -fsSL https://raw.githubusercontent.com/kesslerio/attio-mcp-server/main/scripts/install-claude-desktop.sh | bash
curl -fsSL https://raw.githubusercontent.com/kesslerio/attio-mcp-server/main/scripts/install-cursor.sh | bash
curl -fsSL https://raw.githubusercontent.com/kesslerio/attio-mcp-server/main/scripts/install-claude-code.sh | bash
These scripts will:
attio-mcp npm package globally (if needed)Best for: Power users who prefer full control or use unsupported clients.
npm install -g attio-mcp
~/Library/Application Support/Claude/claude_desktop_config.json~/.config/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"attio-mcp": {
"command": "attio-mcp",
"env": {
"ATTIO_API_KEY": "your_api_key_here"
}
}
}
}
npm install -g attio-mcp
Location: ~/.cursor/mcp.json
{
"mcpServers": {
"attio-mcp": {
"command": "attio-mcp",
"env": {
"ATTIO_API_KEY": "your_api_key_here"
}
}
}
}
echo '{"command":"attio-mcp","env":{"ATTIO_API_KEY":"your_key_here"}}' | claude mcp add-json attio-mcp --stdin -s user
Edit ~/.claude/settings.json:
{
"mcpServers": {
"attio-mcp": {
"command": "attio-mcp",
"env": {
"ATTIO_API_KEY": "your_api_key_here"
}
}
}
}
For development or custom deployments:
git clone https://github.com/kesslerio/attio-mcp-server.git
cd attio-mcp-server
npm install
npm run build
Run directly:
ATTIO_API_KEY=your_key node dist/index.js
# Global installation for CLI usage
npm install -g attio-mcp
# Or local installation for project integration
npm install attio-mcp
Best for: Teams needing centralized OAuth, multi-user access, mobile access, or running MCP without local installation.
Deploy your own Attio MCP server on Cloudflare Workers with full OAuth 2.1 support.
Mobile Access: With a remote MCP server, you can use Attio tools from:
cd examples/cloudflare-mcp-server
npm install
wrangler kv:namespace create "TOKEN_STORE"
# Update wrangler.toml with the KV namespace ID
wrangler secret put ATTIO_CLIENT_ID
wrangler secret put ATTIO_CLIENT_SECRET
wrangler secret put TOKEN_ENCRYPTION_KEY
wrangler deploy
After deployment, configure your client with your Worker URL:
See Cloudflare Worker Deployment Guide for:
records_get_attribute_options tool (#975) - Get valid options for select/status fields with enhanced error messages--option-fetch-delay flagsnake_case, verb-first naming (old names work via aliases until v2.0.0)select_title_to_array for clarityThe server advertises one resource-first catalog. search, fetch, and aaa-health-check are unchanged.
Prior default-catalog names still call the same tool through v2.x. They are not listed in tools/list, they do not change arguments, and MCP_DISABLE_TOOL_ALIASES=true makes them fail. They are removable in v3.0.0. Names that were never that default catalog, including search-records, create-record, and records_search_batch, fail immediately.
The full map is MIGRATION-GUIDE.md and src/constants/tool-names.ts.
The server supports two authentication methods—both use the same Bearer token scheme:
Note: If both are set,
ATTIO_API_KEYtakes precedence.OAuth Users: For detailed setup including PKCE flow and token refresh, see OAuth Authentication Guide.
# Option 1: API Key (recommended for most users)
export ATTIO_API_KEY="your_api_key_here"
# Option 2: OAuth Access Token (for OAuth integrations)
# export ATTIO_ACCESS_TOKEN="your_oauth_access_token_here"
export ATTIO_WORKSPACE_ID="your_workspace_id_here"
# Optional: Deal defaults configuration
export ATTIO_DEFAULT_DEAL_STAGE="Interested" # Default stage for new deals
export ATTIO_DEFAULT_DEAL_OWNER="[email protected]" # Default owner email address (see below)
export ATTIO_DEFAULT_CURRENCY="USD" # Default currency for deal values
# Test the MCP server
attio-mcp --help
# Discover your Attio workspace attributes
attio-discover attributes
The MCP server uses field mapping files to translate between natural language and Attio's API field names. This configuration is essential for proper operation.
# 1. Copy the sample configuration to create your user config
cp configs/runtime/mappings/sample.json configs/runtime/mappings/user.json
# 2. Edit user.json to match your workspace's custom fields
# Focus on the "objects.companies" and "objects.people" sections
configs/runtime/mappings/)default.json - Standard Attio CRM fields (loaded first, don't edit)sample.json - Examples with custom field templates (copy from this, not used at runtime)user.json - YOUR workspace-specific overrides (merged on top of default.json)💡 Key Insight:
user.jsonis merged on top ofdefault.json, so only include overrides and additions. Don't duplicate mappings that already exist indefault.json.
The MCP server loads configuration in this order:
default.json - Contains all standard Attio fields (Name, Description, Team, etc.)user.json - Your custom additions/overrides are merged on topExample: If default.json has "Name": "name" and your user.json also has "Name": "name", that's wasted tokens. Only include fields that are:
{
"mappings": {
"attributes": {
"objects": {
"companies": {
"// Only your custom fields - defaults are inherited": "",
"Lead Score": "lead_score",
"B2B Segment": "b2b_segment",
"Industry Vertical": "custom_industry_field"
}
}
},
"lists": {
"// Only your specific lists": "",
"Sales Pipeline": "your-pipeline-list-id"
}
}
}
✅ Good: Only custom/override fields
❌ Wasteful: Duplicating standard fields from default.json
⚠️ Without proper mapping configuration, the MCP server may not work correctly with your custom fields and lists.
Next: Verify your field mappings work by testing with Claude:
"Find companies in our pipeline with lead score > 80"
Add to your Claude Desktop MCP configuration:
Deal Owner Email (for deal owner defaults):
The ATTIO_DEFAULT_DEAL_OWNER should be set to the email address of the workspace member who should own new deals by default. This is typically your own email address or the email address of your sales team lead.
# Example:
export ATTIO_DEFAULT_DEAL_OWNER="[email protected]"
Note: The system will automatically resolve email addresses to workspace member references when creating deals.
Deal Stages:
Deal stages are specific to your workspace. Check your Attio workspace settings or use the discover-attributes command to find available stages for deals.
{
"mcpServers": {
"attio-mcp": {
"command": "attio-mcp",
"env": {
"ATTIO_API_KEY": "your_api_key_here",
"ATTIO_WORKSPACE_ID": "your_workspace_id_here",
"ATTIO_DEFAULT_DEAL_STAGE": "Interested",
"ATTIO_DEFAULT_DEAL_OWNER": "[email protected]",
"ATTIO_DEFAULT_CURRENCY": "USD"
}
}
}
}
"Find all companies in the AI space with 50+ employees that we haven't contacted in 30 days"
"Show me all prospects added yesterday"
"Find companies created in the last 7 days with revenue over $10M"
"Create a task to follow up with Microsoft about the enterprise deal"
"Add John Smith from Google to our Q1 prospect list"
"Create a list of all SaaS companies who opened our last 3 emails but haven't responded"
"Show me engagement metrics for our outbound campaign this month"
"Add all attendees from the conference to our nurture sequence"
"Show me all enterprise customers with upcoming renewal dates in Q1"
"Create tasks for check-ins with accounts that haven't been contacted in 60 days"
"Find all customers who mentioned pricing concerns in recent notes"
"Update all companies with missing industry data based on their domains"
"Export all contacts added this quarter to CSV"
"Merge duplicate company records for Acme Corporation"
This package is published with npm provenance, creating a verifiable chain from source code to published artifact. Verify a release:
# Check provenance attestation on any published version
npm view attio-mcp --json | jq .attestations
# With pnpm (v10+), enforce trust policy at install time
# pnpm trustPolicy: no-downgrade blocks packages published with weaker credentials
For maximum supply chain protection, install with pnpm v10+ which enforces:
trustPolicy: no-downgrade — blocks versions published with weaker credentials than prior versionsminimumReleaseAge — cooldown period before new versions can be installedComprehensive documentation is available in the docs directory:
⚠️ Note: Universal tools documentation is currently being updated to match the latest implementation. Use the API directly or check the source code for the most accurate interface definitions.
📋 Implementation Status: These docs describe the Attio API endpoints. For MCP tool usage, refer to universal tools documentation above.
The shared server uses exact 2.3.1 releases of @modelcontextprotocol/server
and @modelcontextprotocol/core. Types and protocol errors come from the server
package; runtime Zod protocol schemas come from core. The reusable
createServer(context?) factory returns the SDK's low-level Server. The CLI
connects it to StdioServerTransport from @modelcontextprotocol/server/stdio.
This retains the legacy initialize/serve flow; upgrading packages does not
activate protocol revision 2026-07-28.
The v2 client is pinned for tests. The v1 SDK remains a development dependency
for older-client compatibility tests, and the existing Worker transport retains
its optional legacy peer until its transport migration. Neither is a second
runtime owner in the shared server. Domain result schemas, connector content,
and nonretryable uncertain-write results are unchanged. Invalid tool parameters
now receive the SDK's InvalidParams (-32602) protocol error.
After restoring dependencies, build before running the SDK compatibility suite:
bun run build
bun run test:single test/server/sdk-compatibility.test.ts
This suite exercises the built CLI with both SDK client generations, the public library export, and the Worker's built shared-module imports against local HTTP fixtures. After restoring the example's locked development dependencies, also run:
bun run test:sdk:worker
The separate Worker check uses its locked Wrangler/Miniflare toolchain and the
example's 2024-12-01 compatibility date with nodejs_compat. It builds a temporary
bundle and exercises workerd locally: missing/invalid session denial, authorized
legacy initialization/discovery, output schemas, and an uncertain delete sent
exactly once to an intercepted upstream. No credentials or live CRM access are
needed. Neither check certifies modern protocol serving or a production deployment.
See the official v2 migration guide.
git clone https://github.com/kesslerio/attio-mcp-server.git
cd attio-mcp-server
npm install
npm run build
npm run test:offline
For local development and testing with Smithery Playground:
npm run dev # Opens Smithery Playground with local server
See docs/deployment/smithery-cli-setup.md for detailed Smithery CLI development setup.
npm test # Run all tests
npm run test:offline # Run only offline tests (no API required)
npm run test:integration # Integration tests (requires ATTIO_API_KEY)
npm run e2e # E2E tests (requires ATTIO_API_KEY)
For E2E/integration tests, create .env with your ATTIO_API_KEY. See the Testing Guide for detailed setup.
npm run build # Build TypeScript
npm run test # Run all tests
npm run test:offline # Run tests without API calls
npm run analyze:token-footprint # Generate baseline MCP token footprint report
npm run lint # Check code style
npm run check # Full quality check
npm run setup:test-data # Create test data for integration tests
We welcome contributions! Please see our Contributing Guidelines for details on:
This initial release provides a solid foundation for CRM automation.
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
Original Work Attribution: This project is based on initial work by @hmk under BSD-3-Clause license, with substantial modifications and enhancements by @kesslerio. The original BSD license notice is preserved in the LICENSE file as required.
Ready to transform your CRM workflow? Install Attio MCP Server today and experience the future of CRM automation with AI!
npm install -g attio-mcp
AI-powered access to Attio CRM. Manage contacts, companies, deals, tasks, and notes. Search records, update pipelines, and automate workflows for sales and GTM teams.
{ "mcpServers": { "attio-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Attio se ejecuta localmente por stdio.
Última comprobación: 2026-11-14. AI-powered access to Attio CRM. Manage contacts, companies, deals, tasks, and notes. Search records, update pipelines, and automate workflows for sales and GTM teams.