attio
MCP server from hmk/attio-mcp-server
claude mcp add --transport stdio hmk-attio-mcp-server npx attio-mcp-server \ --env ATTIO_API_KEY="YOUR_ATTIO_API_KEY"
How to use
The attio MCP server exposes a conversational interface to the Attio API, enabling MCP clients (such as Claude) to read company records, read company notes, and write company notes using Attio as the backend. It authenticates requests with a bearer token supplied via the ATTIO_API_KEY environment variable. With this server, you can query Attio for company information, retrieve notes associated with a company, and append notes to a company, making it suitable for automated workflows and AI-assisted CRM tasks.
To use it, configure the MCP client to point at the attio MCP server (for example using npx to start the server as shown in the configuration). Provide your Attio API key as an environment variable (ATTIO_API_KEY). The server will then translate MCP requests into Attio API calls, returning the results to the client. Be mindful of the capability flags: the server supports reading company records, reading company notes, and writing company notes; other activities are not enabled by default.
How to install
Prerequisites:
- Node.js (recommended v22 or higher)
- npm
- git
- dotenv (for managing environment variables)
Setup steps:
- Clone the repository:
git clone https://github.com/YOUR_USERNAME/attio-mcp-server.git
cd attio-mcp-server
- Install dependencies:
npm install
- Copy the dotenv template to create your local environment file (optional if you rely on environment variables directly):
cp .env.template .env
- Create a configuration snippet for your MCP client (example for Claude Desktop):
{
"mcpServers": {
"attio": {
"command": "npx",
"args": ["attio-mcp-server"],
"env": {
"ATTIO_API_KEY": "YOUR_ATTIO_API_KEY"
}
}
}
}
- Start the server (per the project instructions, typically via npx or npm scripts as configured in your environment):
dotenv npx @modelcontextprotocol/inspector node PATH_TO_YOUR_CLONED_REPO/dist/index.js
- Ensure your ATTIO_API_KEY is available in the environment where the MCP inspector runs, so the server can authenticate to Attio.
Additional notes
Environment variables and configuration tips:
- ATTIO_API_KEY must be a valid Attio bearer token with the necessary scopes to read companies and write notes.
- If the development server cannot load environment variables, verify that ATTIO_API_KEY is defined in the shell and also exposed to the MCP inspector as described in the README.
- The server currently advertises capabilities for reading company records, reading company notes, and writing company notes. If you need additional actions, you may need to modify or extend the server code.
- When using npx to run the server, ensure network access to install the package if not cached locally.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.