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.

DimensionSoulThe Persistent Memory Layer for Multi-Agent Systems. Give your AI agents a soul that never forgets.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS44 / 100 · D75 / 100 · B
Reliability5 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance7 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • AI agents needing persistent memory (e.g., Cursor, VS Code Copilot)
  • Multi-agent orchestration scenarios
  • Developers wanting token efficiency and fast context loading
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Simple single-session tasks without need for cross-session memory
  • Data-privacy-critical environments where any syncing is undesirable
  • Users expecting built-in cloud service without self-hosted storage
  • 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
  • Local filesystem read/write (stores JSON configs, snapshots, ledger)
  • Can point to remote folders via config (e.g., Google Drive)
  • Optional: access to local Ollama service for embeddings
  • 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
  • Data stored as plain JSON, not encrypted for sensitive info
  • Concurrent writes from multiple agents may cause data conflicts (mitigated by file ownership)
  • Cloud sync may introduce inconsistencies due to sync conflicts
  • Requires Node.js 18+
  • 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, Cursor, VS Code, Open WebUI, LM Studio, Other MCP-compatible hostsClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1911