← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionNotion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.Anytype MCP ServerOfficial MCP server that lets AI assistants manage your encrypted Anytype wiki in natural language.
FMRS64 / 100 · C64 / 100 · C
Reliability8 / 2010 / 20
Security and permissions17 / 2011 / 20
Maintenance10 / 2014 / 20
Documentation16 / 2014 / 20
Setup experience13 / 2015 / 20
Best for
  • 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
  • Users who already rely on Anytype as a personal or collaborative knowledge base
  • Users who want to create and manage Anytype objects quickly with natural language
  • Advanced users running the Anytype desktop app locally who want AI assistant integration
Not for
  • 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
  • Users without Anytype installed or running and unable to obtain an API key
  • Scenarios needing a remotely hosted service instead of a local stdio process
  • Users who want zero configuration without setting environment variables
Required permissions
  • 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
  • Requires an Anytype API key passed via an Authorization: Bearer header
  • Needs access to the local Anytype API service (default http://127.0.0.1:31009)
  • Passes authentication headers through the OPENAPI_MCP_HEADERS environment variable, treated as secret
  • Runs an npx command locally as a stdio subprocess
Risks and side effects
  • 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
  • OPENAPI_MCP_HEADERS contains the API key; leaking this configuration can expose Anytype data
  • The server can create and modify spaces, objects and lists on behalf of the key owner
  • Running npx -y downloads and executes package code from npm
  • Pointing ANYTYPE_API_BASE_URL at an untrusted address can send authentication headers there
Supported clientsClaude Desktop, Cursor, Zed, GitHub Copilot CLIClaude Desktop, Cursor, Windsurf, Raycast, Claude Code, LM Studio, Kiro
Tools90