| FMRS | 69 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 10 / 20 | 10 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 15 / 20 | 14 / 20 |
|---|
| Best for | - Teams that need AI access to one or more MediaWiki wikis.
- Users combining wiki retrieval with controlled content maintenance.
- Users of Claude, Codex, VS Code, Cursor, or other listed MCP clients.
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Knowledge bases or content systems that do not use MediaWiki.
- Workflows requiring writes without configuration or permissions.
- Users expecting client or protocol compatibility that is not evidenced by the source.
| - 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 operations depend on the wiki being public or configured and reachable.
- Write tools require the corresponding MediaWiki permissions; write tools are hidden from tools/list when the default wiki is read-only.
- File uploads require allowed upload directories to be configured.
- Cargo queries may require the runcargoqueries user right.
- Private wikis and authenticated operations require OAuth, tokens, bot passwords, or another configured authentication method.
| - 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 | - In HTTP mode, Authorization Bearer tokens are forwarded to MediaWiki; authentication should be handled by a reverse proxy with TLS termination outside an untrusted network.
- Before exposing HTTP to others, configure allowed hosts and origins to reduce DNS-rebinding and cross-origin risks.
- Write, delete, move, and upload tools can change wiki content or files; use least-privilege credentials.
- Outbound URL fetching and uploads are subject to SSRF and size limits; internal destinations require MCP_TRUSTED_HOSTS.
- Tool responses have content, file-data, request-body, and upload size caps.
| - 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 Code, Codex, Claude Desktop, VS Code, Cursor, Antigravity, OpenCode, Devin Desktop, Zed, LM Studio | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 46 | 11 |
|---|