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.

DimensionNeo ChatA local-first AI chat workspace for models, agents, skills, plugins, search, RAG, voice, memory, and artifacts.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS58 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience10 / 2014 / 20
Best for
  • Individuals or teams who want control over their data and need a self-hosted AI chat workspace
  • Developers familiar with Next.js, React, and TypeScript
  • Users needing multi-provider integration and plugin extensibility
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Public multi-user services requiring a turnkey SaaS security boundary (accounts, tenant isolation)
  • Users who do not want to manage their own deployment and configuration
  • Users needing native agent orchestration (only limited Agent mode in browser)
  • 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
  • Browser storage access (localStorage, IndexedDB, OPFS)
  • Network access to connect to model providers, search, RAG, voice, and MCP servers
  • Server-side API routes execute plugins, MCP, and proxy requests
  • Optional server environment variables for deployment defaults and security
  • Docker deployments may expose port 3000
  • 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
  • Self-hosting entails security responsibilities; public exposure requires additional hardening
  • User-entered provider credentials are encrypted in the browser, but server misconfiguration could expose them
  • Hosted mode depends on shared stores like Upstash and restricts network policies
  • Remote MCP servers can execute tools; configure carefully
  • Data is stored in the browser by default; clearing browser data may cause loss unless backed up or synced
  • 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