Attio MCP Server

A comprehensive Model Context Protocol (MCP) server for Attio, the AI-native CRM. This server enables AI assistants like Claude to interact directly with your Attio data through natural language, providing seamless integration between conversational AI and your CRM workflows.

🎯 What is Attio MCP Server?

Transform your CRM workflows with AI-powered automation. Instead of clicking through multiple screens, simply ask Claude to find prospects, update records, manage pipelines, and analyze your data using natural language commands.

"Find all AI companies with 50+ employees that we haven't contacted in 30 days and add them to our Q1 outreach list"

✨ Core Features & Implementation Status

🎯 Universal Tools Architecture (14 Tools)

68% Tool Reduction: Consolidated 40+ resource-specific tools into 14 universal operations for consistent, powerful CRM management.

• 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

📊 Feature Implementation Status

✅ Fully Implemented

• Companies: Search, Create, Update, Delete, Advanced Search, Relationship Search
• People: Search, Create, Update, Delete, Advanced Search, Relationship Search
• Lists: Full CRUD operations, filtering, advanced filtering, entry management
• Tasks: Create, Update, Delete, Search with universal tools
• Records: Universal CRUD operations across all resource types
• Notes: Create and list operations for all record types
• Batch Operations: Create, Update, Delete with chunking and error handling

🚧 Partially Implemented

• Content Search: Basic implementation available, may not cover all content types
• Timeframe Filters: Date range filtering implemented, some edge cases may exist
• Field Filtering: Basic field selection available, may not support all attribute types

📊 Company Management

• Universal Search: Find companies with search-records and advanced-search
• Full CRUD: Create, read, update, and delete with universal record operations
• Relationship Discovery: Find companies through search-by-relationship
• Batch Operations: Process hundreds of companies with batch-operations
• Detailed Information: Get contact, business, and social info with get-detailed-info

👥 People Management

• Universal Contact Search: Find people by any criteria using universal search tools
• Relationship Tracking: Link people to companies with search-by-relationship
• Activity Timeline: Track interactions with search-by-content and search-by-timeframe
• Advanced Filtering: Multi-attribute search with universal filtering
• Bulk Operations: Efficiently manage contacts with universal batch operations

📋 Lists & Pipeline Management (11 Tools)

• 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

✅ 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

⚠️ Known Limitations & Important Notes

Current Limitations

• Field Parameter Filtering: Tasks endpoint /objects/tasks/attributes has limitations, handled with fallback patterns
• Pagination: Tasks pagination uses in-memory handling due to API constraints

API Compatibility

• Universal Tools: Primary interface (14 tools) - recommended for all new integrations
• Legacy Tools: Available via DISABLE_UNIVERSAL_TOOLS=true environment variable (deprecated)
• Lists API: Fully functional with complete CRUD operations (contrary to some outdated documentation)

Performance Considerations

• Batch Operations: Optimized with chunking, rate limiting, and error recovery
• Large Datasets: Automatic pagination and field filtering for optimal performance
• Rate Limiting: Built-in protection against API rate limits with exponential backoff

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

🎯 Mastering Advanced Search Filters

The Power Behind Precise CRM Queries - Stop wrestling with complex data searches. Our advanced filtering system lets you find exactly what you need with surgical precision.

"Find all AI companies with 50+ employees that we haven't contacted in 30 days and add them to our Q1 outreach list" - This kind of complex query is exactly what advanced search filters excel at.

🏗️ Filter Architecture

Every advanced search follows this proven pattern that's been battle-tested across thousands of CRM queries:

{
  "resource_type": "companies",
  "filters": {
    "filters": [
      {
        "attribute": { "slug": "field_name" },
        "condition": "operator",
        "value": "search_value"
      }
    ]
  }
}

⚡ Real-World Examples

🔍 Single Criteria Search

{
  "resource_type": "companies",
  "filters": {
    "filters": [
      {
        "attribute": { "slug": "name" },
        "condition": "contains",
        "value": "Tech"
      }
    ]
  }
}

🎯 Multi-Criteria Power Search (AND Logic)

{
  "resource_type": "companies",
  "filters": {
    "filters": [
      {
        "attribute": { "slug": "name" },
        "condition": "contains",
        "value": "Tech"
      },
      {
        "attribute": { "slug": "employee_count" },
        "condition": "greater_than",
        "value": 50
      },
      {
        "attribute": { "slug": "industry" },
        "condition": "equals",
        "value": "AI/Machine Learning"
      }
    ]
  }
}

🚀 Flexible OR Logic

{
  "resource_type": "companies",
  "filters": {
    "filters": [
      {
        "attribute": { "slug": "name" },
        "condition": "contains",
        "value": "Tech"
      },
      {
        "attribute": { "slug": "name" },
        "condition": "contains",
        "value": "AI"
      }
    ],
    "matchAny": true
  }
}

🧠 Smart Filter Operators

Operator	Perfect For	Example Use Case
contains	Text searches	Finding companies with "Tech" in name
equals	Exact matches	Specific industry classification
starts_with	Prefix searches	Companies beginning with "Acme"
ends_with	Suffix searches	Companies ending with "Inc"
greater_than	Numerical analysis	Companies with 100+ employees
less_than	Size filtering	Startups under 50 people
is_empty	Data cleanup	Find records missing key information
is_not_empty	Completeness checks	Records with populated fields

💡 Pro Tips for Different Teams

🎯 Sales Teams - Use these field combinations:

• Companies: name, industry, employee_count, website, location
• People: full_name, job_title, email, company

📈 Marketing Teams - Focus on engagement fields:

• Activity tracking: last_interaction, email_status, campaign_response
• Segmentation: industry, company_size, location, engagement_score

✅ Customer Success - Monitor health metrics:

• Account health: renewal_date, support_tickets, usage_metrics
• Risk indicators: last_contact, satisfaction_score, contract_value

🚨 Avoid These Common Mistakes

❌ Wrong (Flat object structure):

{
  "filters": {
    "name": { "operator": "contains", "value": "Test" }
  }
}

✅ Correct (Nested array structure):

{
  "filters": {
    "filters": [
      {
        "attribute": { "slug": "name" },
        "condition": "contains",
        "value": "Test"
      }
    ]
  }
}

🔧 Quick Troubleshooting

Getting "Filters must include a 'filters' array property"?

1. ✅ Ensure your filters object contains a filters array
2. ✅ Each array item needs attribute, condition, and value
3. ✅ The attribute must be an object with a slug property
4. ✅ Double-check your JSON structure matches the examples above

💬 Pro Tip: Start with simple single-filter searches, then build complexity once you're comfortable with the structure.

🏆 Latest Updates - Critical Issues Resolved

✅ 100% Integration Test Pass Rate Achieved - All critical API contract violations and build issues have been resolved:

Recently Fixed Issues (August 2025)

• P0 Critical API Failures: Fixed response data structure handling for robust fallback patterns
• Build Compilation Errors: Created missing enhanced-validation module and resolved TypeScript compilation
• E2E Test Implementation: Fixed JSON truncation, resource mappings, and email validation consistency
• Field Parameter Filtering: Resolved tasks attribute handling with special case for missing /objects/tasks/attributes endpoint
• Email Validation Consistency: Fixed batch validation and create/update operation alignment
• Pagination System: Documented tasks pagination limitation with in-memory handling workaround

Test Status

• Integration Tests: 15/15 passing (100% pass rate)
• Build Status: All TypeScript compilation successful
• API Contract: All violations resolved with robust error handling

See TROUBLESHOOTING.md for detailed solutions to these resolved issues.

🚀 Installation

Installing via Smithery

To install Attio CRM Integration Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @kesslerio/attio-mcp-server --client claude

Option 1: NPM (Recommended)

# Global installation for CLI usage
npm install -g attio-mcp-server

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

Option 2: One-Command Script Installation

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

Option 3: Manual Installation

git clone https://github.com/kesslerio/attio-mcp-server.git
cd attio-mcp-server
npm install
npm run build

⚡ Quick Start

Prerequisites

• Node.js (v18 or higher)
• Attio API Key (Get one here)
• Attio Workspace ID

1. Set Environment Variables

export ATTIO_API_KEY="your_api_key_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="user@company.com"     # Default owner email address (see below)
export ATTIO_DEFAULT_CURRENCY="USD"                    # Default currency for deal values

2. Test the Installation

# Test the MCP server
attio-mcp-server --help

# Discover your Attio workspace attributes
attio-mcp-server discover attributes

3. 🎯 CRITICAL: Configure Field Mappings

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.

Quick Setup

# 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

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 "Name": "name" and your user.json also has "Name": "name", 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

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

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.

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

{
  "mcpServers": {
    "attio-mcp": {
      "command": "attio-mcp-server",
      "env": {
        "ATTIO_API_KEY": "your_api_key_here",
        "ATTIO_WORKSPACE_ID": "your_workspace_id_here",
        "ATTIO_DEFAULT_DEAL_STAGE": "Interested",
        "ATTIO_DEFAULT_DEAL_OWNER": "user@company.com",
        "ATTIO_DEFAULT_CURRENCY": "USD"
      }
    }
  }
}

🌟 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

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

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"
"Find all customers who mentioned pricing concerns in recent notes"

For Data Operations

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

🔐 Security & Privacy

• Secure API Authentication: Industry-standard API key authentication
• No Data Storage: Direct API passthrough with no local data retention
• Open Source: Full transparency with Apache 2.0 license
• Optional On-Premises: Deploy in your own infrastructure

📚 Documentation

Comprehensive documentation is available in the docs directory:

Universal Tools (Recommended)

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

• API Overview - High-level API concepts and patterns
• Universal Tools Source - Current implementation reference
• Tool Schemas - Parameter definitions and validation

Getting Started

• Installation & Setup
• Claude Desktop Configuration
• Troubleshooting Guide

API Reference

📋 Implementation Status: These docs describe the Attio API endpoints. For MCP tool usage, refer to universal tools documentation above.

• API Overview - General Attio API concepts
• Companies API - Company record endpoints ✅ Fully Implemented via Universal Tools
• People API - Person record endpoints ✅ Fully Implemented via Universal Tools
• Lists API - List management endpoints ✅ Fully Implemented
• Notes API - Notes endpoints ✅ Basic Implementation
• Tasks API - Task endpoints ✅ Implemented via Universal Tools

Advanced Topics

• Batch Operations - Bulk operations ✅ Implemented with chunking
• Advanced Filtering - Complex queries ✅ Implemented
• Error Handling - Error patterns ✅ Enhanced error handling
• Extending MCP - Customization guide

Deployment

• Docker Guide
• Security Best Practices

🛠 Development

Setup Development Environment

git clone https://github.com/kesslerio/attio-mcp-server.git
cd attio-mcp-server
npm install
npm run build
npm run test:offline

Smithery CLI Development

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.

Testing

The project includes comprehensive testing at multiple levels with 100% E2E test pass rate:

🚀 E2E Test Framework (100% Pass Rate)

Our comprehensive E2E test framework validates all universal tools with real Attio API integration:

# E2E Tests (requires ATTIO_API_KEY in .env file)
npm run e2e                 # Run complete E2E test suite (51 tests, 100% pass rate)
npm test -- test/e2e/suites/universal-tools.e2e.test.ts  # Universal tools E2E tests

# Set up E2E environment
echo "ATTIO_API_KEY=your_api_key_here" > .env
npm run e2e                 # Should show 51/51 tests passing

✅ Comprehensive Coverage:

• Pagination Testing: Validates offset parameter across all universal tools
• Field Filtering: Tests fields parameter for selective data retrieval
• Tasks Integration: Complete lifecycle testing for tasks resource type
• Cross-Resource Validation: Ensures consistent behavior across companies, people, lists, tasks
• Error Handling: Validates graceful error responses and edge cases
• Performance Monitoring: Tracks execution times and API response sizes

🛠️ Enhanced Assertions (7 New Methods):

// Available in test/e2e/utils/assertions.ts
expectValidPagination(result, params); // Validates pagination behavior
expectFieldFiltering(result, fields); // Validates field selection
expectValidTasksIntegration(result); // Tasks-specific validation
expectSpecificError(result, errorType); // Typed error validation
expectOptimalPerformance(result, budget); // Performance validation
expectValidUniversalToolParams(params); // Parameter validation
expectValidBatchOperation(result, records); // Batch operation validation

📊 Performance Benchmarks:

• Search Operations: < 1000ms per API call
• CRUD Operations: < 1500ms per operation
• Batch Operations: < 3000ms for 10 records
• Field Filtering: < 500ms additional overhead
• Pagination: < 200ms additional per offset

Unit & Integration Tests

# Unit Tests (no API required)
npm test                    # Run all tests
npm run test:offline        # Run only offline tests (206 tests)
npm run test:watch          # Watch mode for development

# Integration Tests (requires API key and test data)
npm run test:integration    # Run all integration tests (15 tests, 100% pass rate)
npm run setup:test-data     # Create test data in your workspace

Test Environment Setup

For E2E and integration tests, you need:

1. Create .env file in project root:

# Required for E2E/Integration tests
ATTIO_API_KEY=your_64_character_api_key_here
PORT=3000
LOG_LEVEL=debug
NODE_ENV=development

2. Verify API key format (must be exactly 64 characters)
3. Run tests to validate setup:

npm run build && npm run test:integration

See the Testing Guide and E2E Troubleshooting Guide for detailed setup instructions.

Available Scripts

npm run build          # Build TypeScript
npm run test           # Run all tests
npm run test:offline   # Run tests without API calls
npm run lint           # Check code style
npm run check          # Full quality check
npm run setup:test-data # Create test data for integration tests

🤝 Contributing

We welcome contributions! Please see our Contributing Guidelines for details on:

• Adding new tools and features
• Improving documentation
• Reporting bugs and requesting features
• Testing and quality assurance

📈 What's Next?

This initial release provides a solid foundation for CRM automation.

🔗 Links

• NPM Package: https://www.npmjs.com/package/attio-mcp
• GitHub Repository: https://github.com/kesslerio/attio-mcp-server
• Issues & Support: https://github.com/kesslerio/attio-mcp-server/issues
• Releases: https://github.com/kesslerio/attio-mcp-server/releases
• Attio Documentation: https://developers.attio.com/

📄 License

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