Attio MCP Server

Created By
kesslerioa year ago
Attio Model Context Protocol (MCP) server implementation
Overview

What is Attio MCP Server?

Attio MCP Server is an implementation of the Model Context Protocol (MCP) designed for Attio, an AI-native CRM. It allows AI assistants to interact seamlessly with Attio data, enhancing the capabilities of conversational AI in managing customer relationships.

How to use Attio MCP Server?

To use the Attio MCP Server, install it via npm, configure it with your Attio API key, and run it to enable AI assistants like Claude to query and manage your CRM data.

Key features of Attio MCP Server?

  • Comprehensive support for Attio API, including managing companies, people, lists, and tasks.
  • Enhanced capabilities such as robust error handling, automatic retry logic, and input validation.
  • Standardized response formatting for easier integration with AI assistants.

Use cases of Attio MCP Server?

  1. Querying CRM data using natural language.
  2. Adding notes and managing records through AI interactions.
  3. Integrating AI assistants with CRM for improved customer engagement.

FAQ from Attio MCP Server?

  • What is the prerequisite for using Attio MCP Server?

    You need Node.js (v18 or higher) and an Attio API Key to get started.

  • Can I deploy Attio MCP Server using Docker?

    Yes! There are guides available for deploying with Docker and local development.

  • Is there documentation available?

    Yes, full documentation is provided in the docs directory, covering installation, API references, and troubleshooting.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kesslerio
Star
1
Language
TypeScript
License
BSD-3-Clause license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago