← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionClawBioA local-first AI skill library for bioinformaticsBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS63 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Researchers needing local-first and reproducible bioinformatics workflows
  • Users who want an AI agent to orchestrate existing bioinformatics skills
  • Developers learning genome-analysis workflows with demo data
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users seeking a general database, cloud-storage, or browser-automation server
  • Clinical diagnosis or prescribing decisions
  • Use cases that require direct patient-genome access by default
  • 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
  • The default mode runs demo data only
  • With CLAWBIO_MCP_ALLOW_LOCAL_FILES=1, skills may read and write local files
  • Depending on the skill invoked, some workflows access external annotation, genomic, or Galaxy services
  • 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
  • Pharmacogenomic and clinical-variant results should not replace professional medical judgment
  • After local-file access is enabled, skills may process or write input and output files
  • Skills using external APIs or Galaxy may send relevant queries or data to external services
  • Some reproductions require the original external inputs or external tools to remain available
  • 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 clientsCursor, Zed, VS Code, Claude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011