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.

Dimensiondraw.io MCP ServerCreate and render live, interactive draw.io diagrams inline in chat.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS68 / 100 · C75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance15 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Users who want inline diagram previews without leaving the chat
  • Teams brainstorming architecture or process diagrams in Claude.ai or Cursor
  • Users comfortable relying on the hosted mcp.draw.io endpoint
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users needing local .drawio files, PNG/SVG/PDF export, or Mermaid/CSV input (use the MCP Tool Server or Assistant Plugins instead)
  • Strict data-residency environments that cannot send diagram XML to the hosted mcp.draw.io endpoint (self-hosting required)
  • MCP hosts without MCP Apps extension support, where diagrams return as text only
  • 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
  • Sends diagram XML data to the hosted mcp.draw.io endpoint unless self-hosted
  • Loads draw.io viewer application code from app.diagrams.net / viewer.diagrams.net by default
  • No local filesystem or system access required when used as the hosted remote server
  • 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
  • Diagram content is sent to draw.io's hosted server when using the default mcp.draw.io endpoint
  • Outbound requests to app.diagrams.net/viewer.diagrams.net load viewer code by default unless built with VIEWER_PATH
  • Inline rendering depends on the host supporting the MCP Apps extension; otherwise only raw XML text is returned
  • 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.ai, Cursor, VS CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools211