| FMRS | 52 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 7 / 20 | 10 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 14 / 20 |
|---|
| Best for | - Small and mid-sized businesses that sell on WhatsApp and are willing to maintain their own VPS
- Teams that need multi-tenant isolation and data sovereignty
- Operators comfortable configuring Supabase, WAHA and an AI provider following the docs
- Service businesses (clinics, real estate, e-commerce, infoproducts) that need audit, RBAC and LGPD features
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Non-technical users who expect a turnkey product without provisioning a server and a Supabase project
- Scenarios requiring an official SLA or vendor-hosted support (the project is community-run and as-is)
- Teams unwilling to configure third-party services (Supabase, AI provider, WAHA, Upstash, Resend and others)
- Users who need fully automatic updates (updates are triggered by a click or by running the update script)
| - 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 | - Root or equivalent access on a VPS (Docker, cron, ports 80/443)
- Supabase project database and auth credentials (4 credentials plus the Session pooler connection string)
- An API key from an AI provider (OpenRouter, Anthropic or OpenAI)
- A WhatsApp number connected by QR code, or credentials for the official Meta Cloud API channel
- Optional: Upstash Redis, Sentry DSN, Resend, and Nuvemshop integration credentials
| - 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 | - Self-hosting makes you the data controller for the instance, carrying LGPD compliance, backup and maintenance duties
- If the cron (event-log-drain) is not installed and running, automations are created but never execute
- Connecting WhatsApp through a non-official engine (WAHA) carries a risk of account ban, mitigated by throttling and jitter
- The Supabase free plan does not back up automatically, so you must schedule backup.sh yourself
- Updates only target published release tags; reverting to an older version requires the explicit --force flag
- Optional Sentry telemetry sends error reports, with CPF, phone and email scrubbed, and can be turned off with SENTRY_DSN=off
| - 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 clients | | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 0 | 11 |
|---|