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 EChartsGenerate visual charts using ECharts with AI MCP dynamically for chart generation and data analysis.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS65 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions10 / 2016 / 20
Maintenance17 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience15 / 2014 / 20
Best for
  • Data analysts, developers, and AI application builders who need quick chart generation.
  • Users who want to integrate chart generation into LLM workflows.
  • Users needing charts exported in multiple formats.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users needing complex interactive charts or real-time data updates.
  • Enterprise users requiring extensive chart storage and management (may need additional MinIO setup).
  • Users wanting fully managed chart hosting (since it generates locally, not relying on cloud services).
  • 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
  • Access to the file system to read config and output files.
  • Access to MinIO service if configured.
  • Network access to install npm packages (if run via npx).
  • 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
  • Since generation is fully local, performance may be limited by local resources.
  • If MinIO is not configured, exported charts are returned as Base64, which may be large and affect response speed.
  • Depends on Node.js environment; ensure version compatibility.
  • 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, Cline, Cherry StudioClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools211