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.

DimensionArionThe first agentic AI desktop app for geospatial analysisBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS37 / 100 · D75 / 100 · B
Reliability3 / 2010 / 20
Security and permissions7 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation9 / 2017 / 20
Setup experience5 / 2014 / 20
Best for
  • Geospatial analysts wanting a unified desktop GIS + AI workflow
  • Developers who want to run local LLMs and connect custom MCP tools
  • Open-source users comfortable building from source under GPL-3.0
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users looking for an MCP server entry to configure in clients like Claude Desktop (Arion is not an MCP server and ships no server manifest)
  • Users who need official turn-key installers (binary releases are not yet published)
  • Non-technical users unwilling to build an Electron app and compile native modules
  • 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 file system read/write for app data (SQLite) and the knowledge base (PGlite)
  • Network access to call cloud LLM provider APIs
  • Access to a local Ollama instance if local models are configured
  • Execution of system GDAL binaries for raster processing
  • Connections to user-defined MCP servers and execution of their tools
  • 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
  • The project is early-stage (v0.0.14); several features (plugin system, Python agent runtimes, SpatiaLite integration) are planned only
  • Building from source is required; native modules (better-sqlite3, keytar) can fail to compile
  • Connecting custom MCP servers executes external code whose safety you must evaluate yourself
  • With cloud LLMs, query content is sent to third-party APIs
  • 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, Codex, Other MCP stdio clients
Tools011