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.

DimensionMCP Metabase ServerComprehensive Metabase access for AI assistants (70+ tools)BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS59 / 100 · C75 / 100 · B
Reliability6 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Organizations using Metabase that want AI-driven interactions with their BI platform
  • Developers building AI agents that need to interact with Metabase data
  • Teams needing automated Metabase administration and monitoring
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users not using Metabase
  • Scenarios requiring real-time, low-latency data queries (this server uses API calls)
  • Teams looking to avoid maintaining a Metabase instance
  • 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 an API key or username/password for the Metabase instance
  • Tools can read and modify dashboards, cards, databases, collections, and users, depending on API token permissions
  • Schema cache may require local filesystem write access (~/.easecloud/metabase-mcp/)
  • 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
  • Accidental modification or deletion of Metabase resources if API token permissions are too broad
  • Write tools can cause irreversible changes if misused
  • Unencrypted API keys could be exposed
  • Potential rate limiting or increased load on the Metabase instance due to frequent requests
  • 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 DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools9511