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.

DimensionDollhouseMCPOpen-source MCP server for modular AI customization via personas, skills, templates, agents, and memories.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS61 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Advanced users who want composable, shareable elements for deep AI customization
  • Security-conscious teams needing permission governance and auditable agent execution
  • Users of MCP clients with full tool-call round-trip support, especially Claude Code
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who require a server officially maintained by an upstream product owner (this is an independent community project)
  • Users relying on Claude Desktop native permission-hook flows (not supported in this release)
  • Beginners wanting a zero-config experience with no understanding of elements and permission policies
  • 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
  • Reads and writes local Markdown/YAML element files in ~/.dollhouse/portfolio/
  • Optionally uses GITHUB_TOKEN for GitHub portfolio sync and community submissions
  • Update/delete/execute MCP-AQL operations require per-operation confirmation by default (auto-approvable via policy)
  • Agent execution may trigger high-risk operations (file deletion, external API calls, system commands), constrained by danger-zone enforcement and autonomy evaluation
  • 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
  • Activating elements immediately changes AI tool access and permissions; misactivating a restrictive element can block operations
  • Third-party elements from the community collection may contain undesirable content or policies; review before installing
  • Agents can execute multi-step tasks autonomously — danger zones and audits exist, but human oversight is still required
  • AGPL-3.0 requires source disclosure for network use; verify compliance for commercial integrations
  • 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 Code, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Windsurf, Cline, LM StudioClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools711