CommunityAbandoned· 1.3y★ 4.3by hmk

Attio MCP

Connects the Attio AI-native CRM for reading company records, managing notes, and logging activities.

View repo Homepage

Safety & Trust

Delv Safety Grade: C

Score 62/100 · assessed 2026-04-28

Maintainer45

Permissions75

Supply chain70

Transparency55

Incidents100

This community-built MCP server connects to Attio's CRM API for reading company records and managing notes. The maintainer 'hmk' appears to be a solo developer with limited public profile, creating meaningful bus factor risk. The server requires an Attio API key with potentially broad CRM access permissions, though the actual scope depends on the key's configuration within Attio's platform. Distribution via npm as a standard package is positive, and the npx install method is convenient. However, documentation appears thin based on the minimal description provided, making it difficult to assess the full scope of API operations. No security incidents are known. The permissions are reasonably scoped to CRM operations (reading records, writing notes, logging activities) rather than filesystem or shell access, which limits blast radius. For production use with sensitive customer data, organisations should audit the code and consider the single-maintainer risk.

Lethal Trifecta (prompt-injection exposure)

TRIFECTA RISK

All three axes present. This server can read private data, ingest attacker-controlled content, and send data outbound. A poisoned input (a GitHub issue, an email, a webpage) can exfiltrate secrets via this chain. Only install with auditing; avoid on shared or cloud agents.

Private dataYes

Reads secrets, credentials, private files

Untrusted inputYes

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

CRM trifecta. Contact records private. Inbound emails / form submissions untrusted. Outbound API broad.

Green flags

Standard npm package distribution with npx install convenience
Scoped to CRM operations without filesystem or shell access
Integrates with established vendor (Attio) rather than custom backend
No known security incidents or malicious activity

Red flags

Solo maintainer 'hmk' with unclear identity and limited public presence
Thin documentation makes full API scope assessment difficult
API key grants potentially broad CRM access depending on Attio configuration
No visible maintenance activity or community engagement metrics provided

Permissions requested

Outbound networkAccess secretsDB readDB write

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx attio-mcp-server

Env vars needed: ATTIO_API_KEY

Review

Attio is a modern CRM built for teams who want structured data without the enterprise bloat. This MCP server gives Claude direct read access to your company records, notes, and activity logs. It's a straightforward bridge: you ask Claude about a contact or company, and it pulls the data straight from Attio's API. I'd reach for this when prepping for sales calls or enriching contact records without tab-switching. Say you're about to jump on a call with a prospect. You can ask Claude to summarise recent notes, list open deals, or pull key contact details. It saves the mental overhead of remembering which CRM tab holds what. The note-logging feature is useful too: you can dictate a call summary to Claude and have it write directly into Attio, though you'll want to review before it commits. The server is read-focused. You can fetch company records, list notes, and log activities, but you're not creating new companies or editing deal stages. That's probably fine for most workflows, but if you need full CRUD operations, you'll be disappointed. The API key setup is standard: grab it from Attio's settings, drop it in your environment variables, and you're done. One quirk: Attio's data model is flexible, which means the MCP server returns whatever fields your workspace defines. If your team has custom attributes or unusual record structures, Claude might need a bit of context to interpret them correctly. It's not a bug, just a consequence of Attio's schema-less design. Who shouldn't bother: anyone not already using Attio. This isn't a CRM replacement or a way to trial Attio's features. It's a connector for existing users who want Claude to read their CRM without opening another window. If you're on Salesforce or HubSpot, this won't help you. If you're on Attio and you spend half your day context-switching between Claude and your CRM, it's worth the five-minute setup.

Verdict

Install this if you're an Attio user who wants Claude to pull CRM data during research or call prep. Skip it if you need full CRM editing powers or you're not already paying for Attio. It does one thing well: reading your CRM without leaving Claude.

Good at

Pulls CRM data into Claude without tab-switching, which is genuinely faster for research and call prep.
Note-logging works well for dictating call summaries or meeting outcomes directly into Attio.
Setup takes five minutes: one API key, one environment variable, no OAuth dance.
Respects Attio's flexible schema, so it works with custom fields and unusual record structures.

Watch out

Read-heavy: you can't create new companies or edit deal stages, so it's not a full CRM interface.
Only useful if you're already paying for Attio; it's not a trial or a standalone tool.
Custom fields might confuse Claude unless you provide context about what they represent.
No built-in caching, so repeated queries hit the API each time, which could slow things down with large datasets.

Use cases

CRM research
note logging
sales prep
contact enrichment

Getting started

1. Grab your Attio API key from your workspace settings (under Integrations > API). 2. Set the environment variable ATTIO_API_KEY in your shell or dotenv file. 3. Run `npx attio-mcp-server` to install, then add it to your Claude Desktop config under mcpServers with the environment variable passed through. 4. Restart Claude Desktop and ask it to list your recent Attio notes or fetch a company record to confirm the connection. 5. Watch out for custom fields: if your Attio workspace uses non-standard attributes, you may need to tell Claude what they mean the first time it encounters them.

Works with

Claude DesktopClaude CodeCursor