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.

DimensionWitsyDesktop AI assistant and universal MCP client for many model providersBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS45 / 100 · D75 / 100 · B
Reliability6 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance11 / 2018 / 20
Documentation12 / 2017 / 20
Setup experience8 / 2014 / 20
Best for
  • Desktop users who want one interface for many model providers
  • Users who want to run Ollama models locally
  • Users needing desktop shortcuts, document retrieval, or agent features
  • Developers integrating desktop AI actions through a localhost HTTP API
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users seeking a standalone MCP server that provides tools to other MCP clients
  • Users seeking a confirmed client-specific MCP server configuration
  • Users who do not want to configure cloud API keys or install a local model runtime
  • 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
  • Cloud models, search, generation, and speech services require the relevant API keys
  • Ollama requires a local installation and model files
  • Local-file RAG and the local filesystem plugin require access to selected files
  • Prompt Anywhere, AI commands, and global shortcuts interact with other desktop applications
  • The local HTTP API listens on localhost port 8090 by default, or the next available port
  • CLI installation may require creating system-level symlinks on macOS or Linux
  • 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
  • User-provided API keys are used with configured third-party services; costs and data handling depend on those providers
  • Local files, prompts, and conversations may be sent to the selected cloud models or services
  • The HTTP API is localhost-only by default; exposing it through a reverse proxy requires user-configured authentication
  • MCP servers, Python execution, agents, and local-file features can expand the actions or data accessible to the model
  • The software is licensed under AGPL-3.0
  • 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