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.

DimensionVexa MCP ServerOpen-source meeting bots and real-time transcription for Google Meet, Teams and ZoomNotion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS57 / 100 · C64 / 100 · C
Reliability9 / 208 / 20
Security and permissions10 / 2017 / 20
Maintenance13 / 2010 / 20
Documentation14 / 2016 / 20
Setup experience11 / 2013 / 20
Best for
  • Teams that want to self-host and fully own their meeting data and transcripts
  • Regulated organizations needing air-gapped meeting intelligence on their own infrastructure
  • Developers wiring meeting transcripts into their own AI agents and knowledge bases
  • 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 only want hosted SaaS and do not need self-hosting (agent-plane features are self-hosted only)
  • Users needing full mid-call bot control or TTS speech into calls (those endpoints return 404 in the open-core stack)
  • Scenarios requiring guaranteed speaker attribution (heavy crosstalk yields empty speakers on roughly 4–7% of rows)
  • 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
  • A Vexa API key is required for the remote MCP endpoint (Authorization: Bearer header, secret)
  • HTTP API calls use the X-API-Key header
  • Self-hosting requires Docker (engine ≥ v26 recommended) or a Kubernetes/OpenShift cluster
  • Transcription requires an STT service or hosted token; recordings require object storage such as MinIO
  • 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
  • A leaked API key lets someone send bots, read transcripts and dispatch agents as you
  • The bot joins calls as a visible participant, so participant knowledge and consent matter
  • Recordings and transcripts may contain sensitive content; self-hosting with your own storage controls the data boundary
  • Agents handling untrusted input (email, web pages) must run propose-only with human approval, otherwise writes can be irreversible
  • In the open-core stack, mid-call bot config and speak endpoints currently return 404 and should not be relied on
  • 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 Code, CodexClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools09