M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionHass MCP ServerControl and query Home Assistant from Claude and other LLMs — a Model Context Protocol (MCP) server.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS52 / 100 · D75 / 100 · B
Reliability7 / 2010 / 20
Security and permissions10 / 2016 / 20
Maintenance7 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Home Assistant users who want natural language control of their smart home
  • Developers who enjoy using AI assistants like Claude
  • Users who need quick troubleshooting of automations and entities
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who do not need AI control
  • Those who cannot manage long-lived tokens or network configuration
  • Those who need offline or fully local environments without exposing server ports (especially in HTTP mode)
  • 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 a Home Assistant Long-Lived Access Token (HA_TOKEN)
  • Needs network access to the Home Assistant instance via HA_URL
  • In HTTP mode, opens a port that must be protected via proxy or VPN to prevent unauthorized access
  • 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
  • If HTTP mode is exposed to the public internet, anyone can control all smart devices (lights, locks, automations, restart HA)
  • Token leakage could lead to full control of Home Assistant
  • Wrong operations could cause device anomalies or unintended automations
  • 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, Cursor, Claude CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1511