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.

DimensiongotoHuman MCP ServerAdd human approvals to AI agents and agentic workflowsNotion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS50 / 100 · D64 / 100 · C
Reliability9 / 208 / 20
Security and permissions10 / 2017 / 20
Maintenance11 / 2010 / 20
Documentation10 / 2016 / 20
Setup experience10 / 2013 / 20
Best for
  • Developers building AI agents that require human supervision
  • Teams wanting to implement approval processes in AI workflows
  • Scenarios needing a customizable approval UI
  • 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
  • Fully automated processes without human intervention
  • Offline or intranet environments (requires network connectivity)
  • On-premise deployments without the hosted service
  • 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 a GOTOHUMAN_API_KEY for authentication and access to forms in your account
  • Requires network access to app.gotohuman.com
  • Write operations involve the gotoHuman service, no direct local file access
  • 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
  • Exposure of API key could lead to unauthorized approval requests
  • Network issues may disrupt communication with the service
  • Over-reliance on the service could cause delays in approvals
  • 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 Desktop, Cursor, WindsurfClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools39