Attio MCP Server

What hmk/attio-mcp-server MCP server does

The hmk/attio-mcp-server MCP server gives MCP-compatible AI clients access to selected Attio CRM operations. Its current scope is limited to company data: clients can retrieve company records, retrieve company notes, and create or update company notes through the Attio API.

The implementation is intended for situations where an assistant needs CRM context or needs to record information against a company. It does not currently cover the broader set of activities listed in the project roadmap.

How it works

The server runs as a Node.js process and communicates with an MCP client. The client sends requests for supported Attio operations, while the server uses the configured API credential to call Attio. The repository shows an npx launch command for the packaged server and a direct node command for running a locally built development version.

Authentication uses an Attio bearer token. The token can be obtained through Attio’s API Explorer or by configuring OAuth and retrieving a token through the Attio API. Requests therefore depend on an API key with the access needed for the company records and notes the client is expected to use.

Setup and configuration

Set the ATTIO_API_KEY environment variable before starting the server. The documented Claude Desktop configuration launches the package with npx and passes the token through the server’s environment:

{
  "mcpServers": {
    "attio": {
      "command": "npx",
      "args": ["attio-mcp-server"],
      "env": {
        "ATTIO_API_KEY": "YOUR_ATTIO_API_KEY"
      }
    }
  }
}

For local development, the repository requires Node.js, with version 22 or newer recommended, plus npm, Git, and dotenv. The development flow copies .env.template to .env, installs dependencies with npm install, and uses npm run build:watch to keep the built output current. The MCP Inspector can then start the compiled dist/index.js file with dotenv. If the environment variable is not loaded, the README instructs developers to set ATTIO_API_KEY in the inspector interface.

Tools and capabilities

The hmk/attio-mcp-server MCP server currently supports these operations:

• Read company records from Attio.
• Read notes associated with companies.
• Write company notes.

The README marks other activities as unsupported. No additional record types, activity operations, or CRM systems are documented, so those should not be assumed to be available.

Limitations and notes

The documented functionality is centered on companies and notes.

The project documents Claude Desktop usage but does not provide client-specific instructions for other MCP applications. The hmk/attio-mcp-server MCP server also requires a valid ATTIO_API_KEY; without a correctly loaded bearer token, Attio requests may not work. Development and production-style usage differ: local development runs the compiled repository output, while the client example starts the package through npx.