Attio MCP

MCP开发工具

提供方 kesslerio

开发工具 stdio · 本地进程 无需鉴权 社区 / 第三方
查看接入方式

Attio Model Context Protocol (MCP) server implementation

一句话选型结论

按资料字段整理

Attio MCP 属于开发工具类 MCP 服务器,stdio · 本地进程,无需鉴权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

developer-toolsattiomcpservercrmai-assistant

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx attio-mcp-server\"

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Attio MCP当前 未标注 stdio · 本地进程 本地部署 有 2026-05-18
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方kesslerio上游标注的维护方 kesslerio
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-18上游最后核验时间

详细介绍

37.0 KB
来自项目仓库与上游目录的原文,未做删改

Attio MCP Server

A 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.

🎯 What is Attio MCP Server?

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"

🚀 ChatGPT Developer Mode Integration

> ⚠️ 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:

  • 🔐 Built-in Approval Flows: MCP safety annotations auto-approve read operations, request approval for writes
  • 🌐 OAuth Integration: Self-hosted OAuth via Cloudflare Worker deployment
  • 💬 Natural Language CRM: Manage your entire Attio workspace through conversational AI
  • 📖 Setup Guide: See ChatGPT Developer Mode docs and Cloudflare Worker Guide

✨ Core Features & Implementation Status

🎯 Universal Tools Architecture (19 Universal Operations)

Focused Tool Surface: Consolidated 40+ resource-specific tools into universal operations, then added scoped high-frequency write tools for safer company and deal updates.

  • High Performance: 89.7% speed improvement with 227KB memory reduction (PR #483)
  • Enterprise Quality: 97.15/100 production readiness score with zero breaking changes
  • Clean Architecture: Complete production-test separation with mock factory pattern
  • Structured Results: Every default tool advertises a validated output schema; see the result contract for list, member, diagnostic, and connector outputs, and the preceding sections for universal outputs and prose opt-out
  • Scoped Tool Policy: Add scoped default tools only when the workflow is frequent, a generic write can mutate the wrong object class, and the scoped tool removes a model decision instead of merely renaming a universal call

📊 Feature Implementation Status

✅ Complete CRM Surface Coverage

  • Companies: Search, Create, Update, Delete, Advanced Search, Relationship Search
  • People: Search, Create, Update, Delete, Advanced Search, Relationship Search
  • Deals: Full CRUD operations with intelligent field mapping and stage validation
  • Tasks: Create, Update, Delete, Search with multi-assignee support
  • Lists: Full CRUD operations, filtering, advanced filtering, entry management
  • Notes: Create and list operations for all record types
  • Records: Universal CRUD operations across all resource types
  • Batch Operations: Create, Update, Delete with chunking and error handling
  • Content Search: See the supported-input matrix for resource-specific limits
  • Relationship Navigation: Bidirectional company↔person↔deal relationships
  • Advanced Filtering: Sophisticated query capabilities with intelligent field mapping

📊 Company Management

  • Universal Search: Find companies with records_search and records_search_advanced
  • Scoped Writes: Create and update companies with companies_create and companies_update
  • Full CRUD: Create, read, update, and delete with universal record operations when a scoped tool is not available
  • Relationship Discovery: Find companies through records_search_by_relationship
  • Batch Operations: Process hundreds of companies with records_batch
  • Detailed Information: Get contact, business, and social info with records_get_info

👥 People Management

  • Universal Contact Search: Find people by any criteria using universal search tools
  • Relationship Tracking: Link people to companies with records_search_by_relationship
  • Activity Timeline: Retrieve interaction metadata with records_get_interactions
  • Advanced Filtering: Multi-attribute search with universal filtering
  • Bulk Operations: Efficiently manage contacts with universal batch operations

📋 Lists & Pipeline Management (6 Tools + 8 Deprecated)

  • Active Tools: 4 consolidated tools with auto-mode detection (Migration Guide)
  • list_entries_filter - Unified filtering with 4 modes
  • list_entries_manage - Unified entry management with 3 modes
  • list_entries_list - Retrieve list entries
  • records_get_list_memberships - Find record's list memberships
  • List Configuration Tools (dedicated; universal records_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.
  • Errors distinguish 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.
  • Pipeline Operations: Move deals through sales stages
  • Smart Segmentation: Create and manage targeted contact lists
  • Advanced Filtering: Complex multi-condition filtering with AND/OR logic
  • Entry Management: Add, remove, and update list memberships
  • Deal Tracking: Monitor opportunities and revenue pipeline
  • Deal Defaults: Configurable default stage, owner, and currency for streamlined deal creation
  • Scoped Deal Writes: Create and update deals with deals_create and deals_update

✅ Task Management

  • Universal Task Operations: Create, update, and manage tasks with universal tools
  • Record Linking: Associate tasks with any record type using resource_type parameter
  • Progress Tracking: Monitor completion with universal search and filtering
  • Team Coordination: Streamline follow-ups with consistent universal operations

🔧 Advanced Capabilities

  • Batch Processing: Handle bulk operations with error tracking
  • Enhanced Filtering: Text, numeric, date, boolean, and relationship filters with timeframe search (Issue #475)
  • Data Export: JSON serialization for integrations
  • Real-time Updates: Live data synchronization with Attio

🧠 Claude Skills

Supercharge Claude's Attio knowledge with pre-built skills that prevent common errors and teach best practices.

Skill Purpose Setup
attio-mcp-usage Error prevention + universal workflow patterns Bundled - just use it
attio-workspace-schema YOUR workspace's exact field names and options npx attio-discover generate-skill --all --zip
attio-skill-generator Create custom workflow skills (advanced) Python + prompting

Quick Start (solves "wrong field name" errors):```bash
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.

### 💬 **Pre-Built Prompts** (10 Prompts)

Intelligent shortcuts that help Claude work faster with your CRM data:

- **Search & Find** (5): people_search, company_search, deal_search, meeting_prep, pipeline_health
- **Take Actions** (4): log_activity, create_task, advance_deal, add_to_list with dry-run safety
- **Research & Qualify** (1): qualify_lead with automated web research and BANT/CHAMP frameworks
- **Token-efficient**: 300-700 tokens per prompt with consistent formatting
- **Discoverable**: Claude automatically suggests relevant prompts for your tasks

See Using Out-of-the-Box Prompts for detailed documentation and examples.

## 🎯 **Using Out-of-the-Box Prompts**

**NEW**: 10 pre-built MCP prompts for common Sales workflows. No setup required—just use them!

### Available Prompts

| Prompt               | Description                                     | Key Arguments                                    | Example                            |
| -------------------- | ----------------------------------------------- | ------------------------------------------------ | ---------------------------------- |
| `people_search.v1`   | Find people by title, company, territory        | `query`, `limit`, `format`                       | Find AE in fintech, SF             |
| `company_search.v1`  | Query companies by domain, segment, plan        | `query`, `limit`, `format`                       | Find SaaS companies >100 employees |
| `deal_search.v1`     | Filter deals by owner, stage, value, close date | `query`, `limit`, `format`                       | Find deals >$50k closing Q1        |
| `log_activity.v1`    | Log calls/meetings/emails to records            | `target`, `type`, `summary`, `dry_run`           | Log call with Nina at Acme         |
| `create_task.v1`     | Create tasks with natural language due dates    | `title`, `content`, `due_date`, `dry_run`        | Create task: Follow up tomorrow    |
| `advance_deal.v1`    | Move deal to target stage with next action      | `deal`, `target_stage`, `create_task`, `dry_run` | Advance deal to "Proposal Sent"    |
| `add_to_list.v1`     | Add records to a List by name or ID             | `records`, `list`, `dry_run`                     | Add 5 companies to Q1 Outreach     |
| `qualify_lead.v1`    | Research lead with web + BANT/CHAMP scoring     | `target`, `framework`, `limit_web`, `dry_run`    | Qualify Acme Corp with BANT        |
| `meeting_prep.v1`    | 360° prep: notes, tasks, deals, agenda          | `target`, `format`, `verbosity`                  | Prep for meeting with Acme CEO     |
| `pipeline_health.v1` | Weekly snapshot: created/won/slipped + risks    | `owner`, `timeframe`, `segment`                  | Pipeline health for @me last 30d   |

### Quick Examples```bash
# 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"

Universal Arguments

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 executing

Token Awareness Features

Prompts include built-in token optimization:

  • Budget Guards: Prompts stay within token limits (people_search <500, qualify_lead <400)
  • Dev Metadata: Set MCP_DEV_META=true for token counts in responses
  • Telemetry: Set PROMPT_TELEMETRY_ENABLED=true for usage logging
  • Configurable Limits: Override with MAX_PROMPT_TOKENS environment variable

For complete prompt documentation, see docs/prompts/v1-catalog.md.

⚠️ Known Limitations & Important Notes

Current Limitations

  • Field Parameter Filtering: Tasks endpoint /objects/tasks/attributes has limitations, handled with fallback patterns
  • Pagination: See the collection continuation contract for supported paths and bounded task results

API Compatibility

  • Universal Tools: Primary interface (19 tools) - recommended for all new integrations
  • Legacy clients: follow the migration guide for removed resource-specific tools and supported prior-default aliases
  • Lists API: Fully functional with complete CRUD operations (contrary to some outdated documentation)

🤝 OpenAI MCP Compatibility

  • Developer Mode Ready: Every tool now publishes MCP safety annotations (readOnlyHint, destructiveHint) so OpenAI Developer Mode can auto-approve reads and request confirmation for writes.
  • Full Tool Access (Default): The complete catalogue is exposed by default; use MCP tools/list for the current inventory. Do NOT set ATTIO_MCP_TOOL_MODE in Smithery configuration for full access.
  • Search-Only Mode: To restrict to read-only tools (search, fetch, aaa-health-check), explicitly configure ATTIO_MCP_TOOL_MODE: &#x27;search&#x27; in Smithery dashboard when Developer Mode is unavailable.

Discovering What Tools Can Do (No Trial Calls)

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.
  • Both are static: neither needs a credential nor calls Attio, and neither
    echoes credentials into output or logs.

A listed tool is configured, not granted. Authorization is still enforced on
every call, so a manifest entry can still come back denied.

  • Detailed Guide: See docs/chatgpt-developer-mode.md for environment variables, approval flows, and validation tips.
  • User Documentation: See the ChatGPT Developer Mode docs for a complete walkthrough of approval flows and setup instructions.

Performance Considerations

  • Batch Operations: Optimized with chunking, rate limiting, and error recovery
  • Large Datasets: Compose supported collection pages using the continuation contract
  • Rate Limiting: Built-in protection against API rate limits with exponential backoff

For detailed troubleshooting and solutions, see TROUBLESHOOTING.md and GitHub Issues.

🎯 Advanced Search Filters

Build powerful CRM queries with multi-criteria AND/OR filtering. See the Advanced Search Guide for complete examples and operator reference.

🚀 Installation

> ⚠️ IMPORTANT: Correct Package Name
>
> The npm package name is attio-mcp (not attio-mcp-server).
> The GitHub repository is named attio-mcp-server, but the npm package was renamed to attio-mcp in June 2025.
> Installing attio-mcp-server will give you an outdated v0.0.2 release with only 4 legacy tools.

Client Compatibility

Client Local Install (Tier 1-2) Cloudflare Worker (Tier 3)
Claude Desktop ✅ Recommended ✅ Full support
Claude Web N/A ✅ Full support
ChatGPT (Pro/Plus) N/A ✅ Recommended
Cursor IDE ✅ Full support ✅ Full support
Claude Code (CLI) ✅ Recommended Partial

Choose your installation method:

  • Most users: Use Tier 1 (Shell Installers) - one command, automatic setup
  • Power users: Use Tier 2 (Manual) - full control over configuration
  • ChatGPT/Teams/Enterprise: Use Tier 3 (Cloudflare Worker) - self-hosted, multi-user OAuth

Tier 1: Shell Installers

> Best for: Developers who prefer local installations with automatic configuration.

One-command scripts that install attio-mcp and configure your client automatically.

Claude Desktop```bash

curl -fsSL https://raw.githubusercontent.com/kesslerio/attio-mcp-server/main/scripts/install-claude-desktop.sh | bash


#### Cursor IDE```bash
curl -fsSL https://raw.githubusercontent.com/kesslerio/attio-mcp-server/main/scripts/install-cursor.sh | bash

Claude Code (CLI)```bash

curl -fsSL https://raw.githubusercontent.com/kesslerio/attio-mcp-server/main/scripts/install-claude-code.sh | bash


These scripts will:

- Install `attio-mcp` npm package globally (if needed)
- Backup existing configuration files
- Prompt for your Attio API key
- Configure the MCP server for your client
- Print next steps and restart instructions

---

### Tier 2: Manual Configuration

&gt; **Best for**: Power users who prefer full control or use unsupported clients.

Claude Desktop Manual Setup

#### Step 1: Install attio-mcp```bash
npm install -g attio-mcp

Step 2: Find your config file

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Step 3: Add configuration```json

{
"mcpServers": {
"attio-mcp": {
"command": "attio-mcp",
"env": {
"ATTIO_API_KEY": "your_api_key_here"
}
}
}
}


#### Step 4: Restart Claude Desktop completely (quit and reopen)

Cursor IDE Manual Setup

#### Step 1: Install attio-mcp```bash
npm install -g attio-mcp

Step 2: Edit config file

Location: `~/.cursor/mcp.json````json
{
"mcpServers": {
"attio-mcp": {
"command": "attio-mcp",
"env": {
"ATTIO_API_KEY": "your_api_key_here"
}
}
}
}


#### Step 3: Restart Cursor

Claude Code (CLI) Manual Setup

#### Option A: Using Claude CLI command (recommended)```bash
echo &#x27;{&quot;command&quot;:&quot;attio-mcp&quot;,&quot;env&quot;:{&quot;ATTIO_API_KEY&quot;:&quot;your_key_here&quot;}}&#x27; | claude mcp add-json attio-mcp --stdin -s user

Option B: Manual config edit

Edit ~/.claude/settings.json:```json
{
"mcpServers": {
"attio-mcp": {
"command": "attio-mcp",
"env": {
"ATTIO_API_KEY": "your_api_key_here"
}
}
}
}


Building from Source

For development or custom deployments:```bash
git clone https://github.com/kesslerio/attio-mcp-server.git
cd attio-mcp-server
npm install
npm run build

Run directly:```bash
ATTIO_API_KEY=your_key node dist/index.js


NPM Global Install```bash
# Global installation for CLI usage
npm install -g attio-mcp

# Or local installation for project integration
npm install attio-mcp

Tier 3: Cloudflare Worker (Remote Deployment)

> 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:

  • ChatGPT mobile app (iOS/Android)
  • Claude mobile app (iOS/Android)
  • Any browser on any device

Cloudflare Worker Features

Feature Cloudflare Worker
Setup complexity Medium
OAuth built-in ✅
Mobile app access ✅
Multi-user access ✅
Custom domain ✅
Self-hosted ✅
Team deployments ✅ Full
Cost Free tier

Quick Deploy```bash

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


#### Client Configuration

After deployment, configure your client with your Worker URL:

- **Claude.ai**: Settings → Connectors → Add your Worker URL
- **ChatGPT**: Settings → Connectors → Developer Mode → Add Worker URL

See Cloudflare Worker Deployment Guide for:

- Complete OAuth 2.1 setup with Attio
- Token encryption configuration
- Production deployment checklist
- Troubleshooting guide

---

## 🆕 What&#x27;s New in v1.4.0

### Major Features

- **🎯 Workspace Schema Skill Generator** (#983) - Auto-generate Claude Skills from your Attio workspace schema for error-free field names and options
- **🔍 Select-field Transformer** (#1019) - Case-insensitive matching, partial matching, and UUID pass-through for select/status fields
- **🛠️ Attio Skill Generator Meta-skill** (#1020) - Meta-skill for automatic workspace documentation
- **📚 Universal Usage Guide Skill** (#1018) - Hand-crafted workflow patterns and error prevention
- **⚙️ `records_get_attribute_options` tool** (#975) - Get valid options for select/status fields with enhanced error messages
- **📞 Phone validation** (#951) - Built-in phone number validation support
- **⏱️ Configurable option fetch delay** - Rate limiting control via `--option-fetch-delay` flag

### Major Enhancements

- **🏷️ MCP-compliant tool naming** (#1039) - All tools now use `snake_case`, verb-first naming (old names work via aliases until v2.0.0)
- **🎨 Custom object display names** (#1017) - Fetch display names directly from Attio API
- **📖 Split integration patterns** (#1023) - Progressive discovery patterns by use case
- **💡 Enhanced attribute error messages** (#975) - Levenshtein distance suggestions for typos

### Critical Fixes

- 📝 Note content line breaks preserved (#1052)
- 👤 People search &quot;Unnamed&quot; display fixed (#1051)
- ✅ Select field persistence (#1045)
- 🔗 Record-reference auto-transformation (#997)
- 📊 Multi-select array auto-transformation (#992)
- 🛡️ Complex attribute validation (#991)
- ⚠️ Field persistence false warnings (#995)
- 📦 SDK dependency pinning (#1025)
- 💼 Deal stage/UTM validation (#1043)
- 📍 Location field auto-normalization (#987)

### Internal Improvements

- Tool alias system refactoring (#1041) - Type-safe constants with pattern-based generation
- Strategy Pattern for CRUD error handlers (#1001)
- Consolidated metadata fetching (#984)
- UniversalUpdateService modularization (#984)
- Select transformation type rename (#1055) - `select_title_to_array` for clarity

## Tool names

The 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.

| Prior name              | Canonical name          |
| ----------------------- | ----------------------- |
| `search_records`        | `records_search`        |
| `create_record`         | `records_create`        |
| `get-lists`             | `lists_list`            |
| `manage-list-entry`     | `list_entries_manage`   |
| `get-workspace-member`  | `workspace_members_get` |
| `smithery_debug_config` | `diagnostics_get`       |

The full map is MIGRATION-GUIDE.md and `src/constants/tool-names.ts`.

## ⚡ Quick Start

### Prerequisites

- Node.js (v18 or higher)
- Attio API Key (Get one here) **or** OAuth access token
- Attio Workspace ID

### 🔐 Authentication Options

The server supports two authentication methods—both use the same Bearer token scheme:

| Method                    | Environment Variable | Best For                             |
| ------------------------- | -------------------- | ------------------------------------ |
| **API Key** (recommended) | `ATTIO_API_KEY`      | Long-term integrations, personal use |
| **OAuth Access Token**    | `ATTIO_ACCESS_TOKEN` | OAuth integrations, third-party apps |

&gt; **Note:** If both are set, `ATTIO_API_KEY` takes precedence.
&gt;
&gt; **OAuth Users:** For detailed setup including PKCE flow and token refresh, see OAuth Authentication Guide.

### 1. Set Environment Variables```bash
# Option 1: API Key (recommended for most users)
export ATTIO_API_KEY=&quot;your_api_key_here&quot;

# Option 2: OAuth Access Token (for OAuth integrations)
# export ATTIO_ACCESS_TOKEN=&quot;your_oauth_access_token_here&quot;

export ATTIO_WORKSPACE_ID=&quot;your_workspace_id_here&quot;

# Optional: Deal defaults configuration
export ATTIO_DEFAULT_DEAL_STAGE=&quot;Interested&quot;           # Default stage for new deals
export ATTIO_DEFAULT_DEAL_OWNER=&quot;user@company.com&quot;     # Default owner email address (see below)
export ATTIO_DEFAULT_CURRENCY=&quot;USD&quot;                    # Default currency for deal values

2. Test the Installation```bash

Test the MCP server

attio-mcp --help

Discover your Attio workspace attributes

attio-discover attributes


### 3. 🎯 **CRITICAL: Configure Field Mappings**

The MCP server uses **field mapping files** to translate between natural language and Attio&#x27;s API field names. **This configuration is essential for proper operation.**

#### **Quick Setup**```bash
# 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&#x27;s custom fields
# Focus on the &quot;objects.companies&quot; and &quot;objects.people&quot; sections

Configuration Files (in 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.json is merged on top of default.json, so only include overrides and additions. Don't duplicate mappings that already exist in default.json.

How Configuration Merging Works

The MCP server loads configuration in this order:

  1. default.json - Contains all standard Attio fields (Name, Description, Team, etc.)
  2. user.json - Your custom additions/overrides are merged on top

Example: If default.json has &quot;Name&quot;: &quot;name&quot; and your user.json also has &quot;Name&quot;: &quot;name&quot;, that's wasted tokens. Only include fields that are:

  • New custom fields (not in default.json)
  • Different mappings (overriding default behavior)

Optimized user.json Example```json

{
"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

&gt; ⚠️ **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:```
&quot;Find companies in our pipeline with lead score &gt; 80&quot;

4. Configure Claude Desktop

Add to your Claude Desktop MCP configuration:

Finding Required IDs

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.```bash

Example:

export ATTIO_DEFAULT_DEAL_OWNER="john.smith@company.com"


**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.```json
{
  &quot;mcpServers&quot;: {
    &quot;attio-mcp&quot;: {
      &quot;command&quot;: &quot;attio-mcp&quot;,
      &quot;env&quot;: {
        &quot;ATTIO_API_KEY&quot;: &quot;your_api_key_here&quot;,
        &quot;ATTIO_WORKSPACE_ID&quot;: &quot;your_workspace_id_here&quot;,
        &quot;ATTIO_DEFAULT_DEAL_STAGE&quot;: &quot;Interested&quot;,
        &quot;ATTIO_DEFAULT_DEAL_OWNER&quot;: &quot;user@company.com&quot;,
        &quot;ATTIO_DEFAULT_CURRENCY&quot;: &quot;USD&quot;
      }
    }
  }
}

🌟 Example Use Cases

For Sales Teams```

"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"


### **For Marketing Teams**```
&quot;Create a list of all SaaS companies who opened our last 3 emails but haven&#x27;t responded&quot;
&quot;Show me engagement metrics for our outbound campaign this month&quot;
&quot;Add all attendees from the conference to our nurture sequence&quot;

For Customer Success```

"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"

…(正文过长,页面只展示前面部分,完整内容见仓库)
```

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Attio MCP 怎么安装?

在客户端按下面的安装命令接入:npx attio-mcp-server\"。装完在客户端配置里引用同一个包或端点。

Attio MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Attio MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Attio MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Attio MCP 能提供哪些能力?

资料显示能力标签包括 AI代理、JavaScript、自然语言交互。具体工具清单以官方文档为准。

Attio MCP 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Attio MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-18。