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.

DimensionClawd CursorSafe cross-OS desktop control for any AI agent — the fallback execution layer.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS68 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions13 / 2016 / 20
Maintenance15 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • AI agents needing cross-platform desktop automation
  • Scenarios requiring safety controls with allow/confirm/block
  • Privacy-sensitive tasks that should stay local
  • Agents wanting to avoid high vision model costs
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Browser-only automation where specialized tools exist
  • Cloud-hosted or non-local execution
  • Tasks requiring strict human approval
  • Pure pixel-based manipulation without vision models
  • 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
  • Desktop control (click, type)
  • Read screen content (accessibility tree, OCR, screenshots)
  • Open apps and files
  • Browser control (CDP)
  • Clipboard read/write
  • System-level hotkeys
  • 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
  • Agent may perform unintended actions, leading to data loss or system changes
  • Sensitive information on screen could be read by the agent
  • Potential for malicious actions if agent misbehaves
  • Requires proper permission grants, otherwise may not work
  • Confirmation mode may interrupt automation flow
  • 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, Claude Code, Cursor, Windsurf, Zed, CodexClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1411