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.

DimensionMCPProxyLocal-first MCP proxy with BM25 tool discovery, security scanning, quarantine & ~99% token savingsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS62 / 100 · C76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance13 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers and teams that need a unified, secure entry point in front of many MCP servers
  • Security-conscious users worried about Tool Poisoning Attacks who want new servers quarantined by default
  • AI agent users limited by context windows or client tool caps who want large token savings
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users who want a fully cloud-hosted setup and will not run a local proxy
  • Lightweight setups connecting only one or two simple MCP servers where discovery, quarantine and auditing add no value
  • Environments where running a Go binary or local service is not possible
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Read and write the local config directory ~/.mcpproxy/ (mcp_config.json, certificates, activity logs)
  • Listen on a local HTTP port (127.0.0.1:8080 by default)
  • Spawn local stdio upstream MCP servers using the commands in your configuration
  • Connect to remote HTTP upstream servers as configured, potentially including OAuth login
  • If HTTPS is enabled, add a self-signed CA certificate to the system keychain via mcpproxy trust-cert
  • If third-party scanners are enabled, a working Docker environment is required
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • The proxy becomes the single channel for all upstream tools, so a misconfiguration could expose tools the agent should not reach
  • The proxy inspects tool arguments and responses for sensitive data, and sensitive content may end up in the local activity log
  • Quarantine blocks new servers, but an already-approved server that later changes still requires re-approval (the README notes tool changes trigger blocking)
  • Spawning stdio upstreams means the proxy can execute the commands in your config, so the config source must be trusted
  • HTTPS uses self-signed certificates that must be manually trusted, otherwise clients fail to connect
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsCursor, Claude Desktop, VS Code, GooseClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools515