| FMRS | 63 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 10 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 |
|---|
| Maintenance | 15 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Home Assistant users who want AI-assisted configuration and maintenance
- Users who need automation debugging, history queries, and system-management capabilities
- Users running Home Assistant OS, Supervised, Container, or Core
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Users who only need voice-style control of devices already exposed to Assist
- People who do not use Home Assistant
- Users requiring the server to be an official Home Assistant product
| - 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 | - Requires access to Home Assistant APIs and entity, service, and configuration capabilities
- Control, configuration changes, deletion, restart, and backup operations may require substantial privileges
- File and YAML tools require the custom component and beta feature flags
- Read-only mode, per-tool controls, and tool security policies can be enabled
| - 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 | - Write, delete, restart, restore, and YAML-editing operations can change or disrupt the smart-home configuration
- File and YAML tools are disabled by default; when enabled, restrict allowed paths and retain backups
- stdio has known connection issues; the custom component or HTTP methods are recommended for real setups
- Multiple installation entries for the same client can cause connection hangs
| - 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.ai, ChatGPT, Claude Code, Gemini CLI, Open WebUI, VS Code, Cursor | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 87 | 11 |
|---|