M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionRelaticleOpen-source CRM your AI agents can write to via MCPNotion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS49 / 100 · D64 / 100 · C
Reliability8 / 208 / 20
Security and permissions7 / 2017 / 20
Maintenance12 / 2010 / 20
Documentation11 / 2016 / 20
Setup experience11 / 2013 / 20
Best for
  • Developer-led teams
  • AI-forward startups
  • SMBs wanting AI agent integration without vendor lock-in
  • Organizations needing self-hosted, data-sovereign CRM
  • 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 who want a fully managed SaaS and do not want to run infrastructure
  • Environments that cannot meet PHP 8.5+ and PostgreSQL 17+ requirements
  • Users needing multi-language UI out of the box (the main repository ships English-only; a lang directory must be added)
  • 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
  • Access to CRM data on the self-hosted server (companies, people, deals, tasks, notes, etc.)
  • Write operations on CRM records through the MCP server
  • Full CRUD and schema access through the REST API
  • Team-scoped data and workspace access under multi-team isolation
  • 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
  • The MCP server can write to CRM data, so misconfiguration may cause unintended record changes or deletions
  • Exposed MCP endpoints (https://mcp.relaticle.com) require your own authentication and access controls
  • Self-hosting means patching, backups, and infrastructure maintenance are the deployer's responsibility
  • The AGPL-3.0 license imposes obligations for redistribution and network services
  • 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 clientsClaude DesktopClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools09