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.

DimensionBilig WorkPaper ServerFormula readback, input edits, JSON persistence, and workbook risk preflight for agents.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS67 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Node.js services that want to own backend workbook calculations without a UI.
  • AI agents that need tools to interact with spreadsheets with formula readback.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Use cases requiring a visual spreadsheet interface or Office macros.
  • Workflows that require exact Excel parity.
  • 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 and write workbook inputs and formulas.
  • Write access to a specified WorkPaper JSON file if persistence is used.
  • No authentication is required for the hosted mode.
  • 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
  • Formula compatibility is limited; some formulas may be unsupported.
  • Persistence in file-based mode could overwrite unexpected files if the path is misconfigured.
  • Embedded XLSX formulas might not be trustworthy; use Excel oracle for accuracy.
  • 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, Generic MCP ClientClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools811