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 Server for ExcelAI-driven Excel automation on Windows, powered by the real Excel COM engine.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS60 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions9 / 2016 / 20
Maintenance15 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Data analysts automating repetitive Excel workflows
  • Developers building Excel-based data solutions
  • Business users managing complex Excel workbooks
  • Teams maintaining Power Query/VBA/DAX code in Git
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Server-side data processing (use libraries like ClosedXML or EPPlus instead)
  • Linux or macOS users (Windows plus a local Excel install is required)
  • High-volume batch processing workloads
  • 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
  • Controls the local Excel.Application process via Windows COM automation
  • Requires exclusive access to the Excel workbook files it operates on
  • Creates and modifies workbook files (e.g. .xlsx) on disk during automation
  • 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
  • Drives a real local Excel process and edits real workbooks, so files should be backed up or version-controlled before automation
  • Supports running VBA macros, which can execute arbitrary code if the macro source is untrusted
  • Not an official Microsoft product — maintained by an independent community developer, not Excel or MCP's upstream owner
  • Requires exclusive workbook access, which can conflict with other processes that have the file open
  • 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, VS Code, GitHub CopilotClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools211