attio

This MCP server exposes the Attio API as a suite of human-readable tools that AI copilots can call to manage your Attio workspace. Each tool is named and categorized for easy discovery, such as list_objects or create_task, covering core data management (objects, records, attributes), lists and entries (lists and list entries), collaboration (tasks, notes, comments), and administrative actions (workspace members, webhooks, current user). The server is designed for high performance with Bun and TypeScript, enabling responsive interactions for AI assistants like Claude Desktop and Cursor. To use it, provide your Attio access token via the environment and then run the server. Tools can be invoked through the MCP protocol by category and action, returning structured data that can be consumed by your assistant or workflows.

Once running, Claude or Cursor can query objects, update records, manage lists and tasks, fetch notes and comments, and configure webhooks or authentication details through the exposed endpoints. The human-readable tool names abstract away Attio's API endpoints, making it easier to compose complex workflows without deep API knowledge.

Prerequisites:\n- Node.js or Bun installed on your machine. This server is built with Bun and TypeScript, but you can run a compatible Node-based start if needed.\n- Attio API access token (see below).\n\n1. Clone the repository:\n``` git clone https://github.com/user-attachments/itsbrex-attio-mcp-server.git cd itsbrex-attio-mcp-server

2. Install dependencies (choose Bun if available):\n```
# Using Bun (recommended for this project)
bun install

or (if Bun is not available, fall back to npm/node if configured):\n``` npm install

3. Build the server (if applicable):\n```
bun run build

4. Create or update your environment file with the required token and settings. At minimum, set ATTIO_ACCESS_TOKEN.\n``` ATTIO_ACCESS_TOKEN=your_token_here

5. Start the server:\n```
bun start

If you’re using Node directly and the project provides a start script, you might use:\n``` npm run start

6. Verify the server is running by curling the health endpoint or checking logs. The server should listen on port 3000 by default unless configured otherwise.\n\nOptional: integration with Claude Desktop or Cursor via their installation scripts as documented in the repository (see Quick Start for ./install.sh and per-client install scripts).

Tips and considerations:\n- Ensure ATTIO_ACCESS_TOKEN is kept secret and not committed to version control.\n- If you encounter authentication errors, regenerate the token from your Attio account and update the environment.\n- The server exposes a rich set of tools; if you don’t see a tool you expect, ensure the API scope covers it or that the build includes the latest endpoints.\n- Typical ports and logging: PORT can be overridden via environment; LOG_LEVEL controls verbosity.\n- When testing with Claude or Cursor, restart the client after installing or updating configuration to pick up new tools.\n- For development, edit src/index.ts to customize endpoints or add tooling; run bun run build and bun test to verify changes.