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.

DimensionMetaMCPA self-hosted gateway that aggregates MCP servers into unified endpoints.Context7Upstash's official server providing up-to-date third-party library docs for AI coding assistants
FMRS60 / 100 · C80 / 100 · B
Reliability10 / 2014 / 20
Security and permissions12 / 2016 / 20
Maintenance10 / 2017 / 20
Documentation15 / 2015 / 20
Setup experience13 / 2018 / 20
Best for
  • Developers and organizations that need self-hosted MCP infrastructure.
  • Teams that centrally manage multiple MCP servers, namespaces, endpoints, and access keys.
  • Deployments that need authentication, rate limiting, and tool-selection controls around MCP access.
  • Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
  • Scenarios wanting zero-config documentation lookup
Not for
  • Users who only need a single MCP server without aggregation or gateway features.
  • Deployments that cannot run Docker or provide the required runtime environment.
  • STDIO-only client environments where a local proxy cannot be used.
  • Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
  • Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
Required permissions
  • Access to configured upstream MCP servers.
  • Permission to start configured commands and dependencies for STDIO MCP servers.
  • Access to container environment variables containing secrets and other configuration.
  • Handling of sessions, API keys, or OIDC login data when authentication is enabled.
  • Network access, Docker, and persistent PostgreSQL storage for deployment.
  • Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
  • Read-only documentation lookup — no code execution or local filesystem access involved
Risks and side effects
  • Misconfiguration can expose multiple upstream MCP servers or tools through one public endpoint.
  • Poor handling of environment variables or API keys can disclose credentials.
  • Public endpoints may face unauthorized calls, excessive traffic, or misuse of upstream tools.
  • Rate-limit counters are stored in memory, and each cluster machine counts traffic independently.
  • Running STDIO servers and their dependencies expands the container's execution and network-access scope.
  • The free tier has limited quota — high-frequency use may hit rate limits
  • Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
Supported clientsCursor, Claude DesktopClaude Code, VS Code, Cursor, Cline, Amp
Tools02