← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionAnytype MCP ServerOfficial MCP server that lets AI assistants manage your encrypted Anytype wiki in natural language.WhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS64 / 100 · C64 / 100 · C
Reliability10 / 2010 / 20
Security and permissions11 / 2012 / 20
Maintenance14 / 2012 / 20
Documentation14 / 2016 / 20
Setup experience15 / 2014 / 20
Best for
  • 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
  • Individuals who want to talk to Claude from their personal WhatsApp number
  • Developers comfortable configuring from a terminal and using the Claude Code development flag
  • Automation scenarios needing remote tool approval from a phone
Not for
  • 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
  • Compliance scenarios requiring the official WhatsApp Business API or a Meta developer account
  • Teams needing officially hosted, multi-tenant, or cloud multi-instance deployment
  • Environments unable to guarantee only one client instance at a time
  • Users expecting voice transcription without setting up mlx-whisper themselves
Required permissions
  • 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
  • Read and send WhatsApp messages as your personal number
  • Access the local runtime state directory ~/.whatsapp-channel/ (auth, allowlists, group configs, inbox)
  • Read and write local repository files and run scripts (e.g. bun scripts/access.ts, scripts/watchdog.sh)
  • Optional local voice transcription (ffmpeg and an mlx-whisper environment)
Risks and side effects
  • 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
  • Messages Claude sends appear from your own number and are indistinguishable to recipients
  • WhatsApp allows one linked-device session per account; running two servers makes them kick each other off
  • Access-control commands are deliberately not MCP tools (terminal-only); exposing them to the message side risks prompt injection
  • Session waking depends on the Claude Code channel extension; other clients get no push
  • A known Claude Code client bug (#37933) may cause messages not to arrive, a client-side issue
  • Launching with --dangerously-load-development-channels carries risk, so verify the source is trustworthy
Supported clientsClaude Desktop, Cursor, Windsurf, Raycast, Claude Code, LM Studio, KiroClaude Code, Codex, Gemini CLI, Cursor
Tools010