| FMRS | 52 / 100 · D | 64 / 100 · C |
|---|
| Reliability | 7 / 20 | 8 / 20 |
|---|
| Security and permissions | 11 / 20 | 17 / 20 |
|---|
| Maintenance | 10 / 20 | 10 / 20 |
|---|
| Documentation | 12 / 20 | 16 / 20 |
|---|
| Setup experience | 12 / 20 | 13 / 20 |
|---|
| Best for | - Attio users looking to automate CRM workflows with AI assistants, reducing manual input
- Teams needing integration with Claude Desktop, Cursor, or Claude Code
- Those who want to query CRM data and manage deals, lists, and tasks via natural language
| - Teams and individuals who already manage docs/wikis in Notion and want AI clients (Claude Desktop, Cursor, etc.) to operate on that content directly
- Developers who want to self-host a local MCP server rather than use a remote hosted option
- Automation/agent workflows that need to query or update Notion database records programmatically
|
|---|
| Not for | - Users without an Attio account or API key
- Scenarios requiring local data storage or offline operations (server proxies API, does not store data)
- Those who wish to restrict to read-only tools (can be achieved by setting `ATTIO_MCP_TOOL_MODE=search`)
| - Users who want the standard-OAuth, zero-JSON-config install with active official support — Notion recommends its newer remote Notion MCP server for that
- Users uncomfortable handing a Notion integration token to a locally-run LLM client
- Use cases needing capabilities the integration deliberately excludes, such as deleting databases
- Long-term production deployments that need guaranteed maintenance, given this repo may be sunset
|
|---|
| Required permissions | - Requires `ATTIO_API_KEY` environment variable (required API key)
- Optional workspace ID: `ATTIO_WORKSPACE_ID`
- Optional tool mode: `ATTIO_MCP_TOOL_MODE` ('full' or 'search')
- Optional log level: `MCP_LOG_LEVEL`
- Options for default deal stage, owner, currency can be configured
| - A Notion internal integration token (NOTION_TOKEN or the Authorization value in OPENAPI_MCP_HEADERS), scoped by that integration's Capabilities (can be limited to read-only)
- Access limited to the specific pages/databases explicitly connected to the integration, not the whole workspace
- A separate bearer auth token when using the Streamable HTTP transport (--auth-token / AUTH_TOKEN)
- Network access to the Notion API
|
|---|
| Risks and side effects | - API key exposure: if the API key is shared or exposed, others could access your CRM data
- Data modification risk: default tool mode allows write operations (create, update, delete), potentially leading to accidental changes
- Third-party dependency risk: open-source project, self-audit required
- Configuration error risk: improper field mapping configuration can lead to API call failures
| - If the integration is granted broad read/write capabilities and connected to many pages, that content is effectively exposed to the LLM, risking data leakage or unintended edits
- Running with --unsafe-disable-auth removes bearer authentication on the HTTP transport, potentially making it reachable via DNS rebinding from pages a user visits — the README says to only use it on an isolated network
- Multi-tenant token passthrough requires careful TLS/gateway configuration; misconfiguration risks leaking or misrouting Notion tokens between tenants
- The README states this local server may be sunset in favor of the remote Notion MCP, and that issues/PRs here are not actively monitored, so long-term maintenance and security fixes are not guaranteed
- Storing NOTION_TOKEN or OPENAPI_MCP_HEADERS directly in shared client config files risks leaking the secret
|
|---|
| Supported clients | Claude Desktop, Claude Web, Cursor, Claude Code | Claude Desktop, Cursor, Zed, GitHub Copilot CLI |
|---|
| Tools | 24 | 9 |
|---|