← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionWhatsApp MCPRead, search, and send WhatsApp messages via ClaudeBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS54 / 100 · D75 / 100 · B
Reliability7 / 2010 / 20
Security and permissions11 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience10 / 2014 / 20
Best for
  • Individual users who want to manage WhatsApp messages with an AI assistant while keeping local message records
  • Developers needing programmatic access to WhatsApp chat data
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Environments with high security requirements for WhatsApp messages (prompt injection risks)
  • Large enterprise deployments requiring official WhatsApp API support (this server uses unofficial Web API)
  • Multi-user setups or those needing fine-grained access control (current implementation is single-user)
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Read and send WhatsApp messages (via bridge)
  • Read and write message history in local SQLite database
  • Send and receive media files
  • Access local file system (for media file paths)
  • Listen on local REST API port (default 8080)
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • Prompt injection: malicious messages could trick the AI into performing unintended actions, leading to data exfiltration
  • Unofficial API: uses reverse-engineered WhatsApp Web API, potentially violating WhatsApp's terms of service
  • Sensitive data exposure: messages are stored locally, but the AI might send content to external services
  • No authentication: the MCP server itself has no authentication, and if exposed to network, it can be abused
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Desktop, CursorClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1411