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 ZoomAnytype MCP ServerOfficial MCP server that lets AI assistants manage your encrypted Anytype wiki in natural language.
FMRS57 / 100 · C64 / 100 · C
Reliability9 / 2010 / 20
Security and permissions10 / 2011 / 20
Maintenance13 / 2014 / 20
Documentation14 / 2014 / 20
Setup experience11 / 2015 / 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
  • 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 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 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 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
  • 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
  • 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
  • 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 Code, CodexClaude Desktop, Cursor, Windsurf, Raycast, Claude Code, LM Studio, Kiro
Tools00