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.

DimensionKindly Web Search MCP ServerWeb search plus robust content retrieval for AI coding tools and agentsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS59 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Users of AI coding tools who need full discussion/documentation context rather than just URLs
  • Clients that support MCP, such as Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and Claude Desktop
  • Teams deploying a remote MCP service via Docker and Streamable HTTP
  • Environments that must egress through a proxy (HTTP/SOCKS5)
  • 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 cannot install a Chromium-based browser on the MCP client machine and mainly need arbitrary-site page_content extraction
  • Users who want to expose the remote HTTP port directly to the public internet (it is unauthenticated and unencrypted by default)
  • Users unwilling to provide any search provider API key
  • 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
  • Reads a search provider API key from the environment (one of Serper/SerpBase/Tavily/SearXNG/Sofya/You.com)
  • Optional GITHUB_TOKEN (can be read-only and limited to public repositories) for GitHub Issues/Discussions extraction
  • Launches a local headless Chromium browser process to fetch arbitrary web pages
  • Optional outbound network access via proxy env vars (HTTP_PROXY/HTTPS_PROXY/ALL_PROXY) or KINDLY_CHROME_PROXY
  • 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
  • HTTP transports are unauthenticated and unencrypted by default; exposing the port publicly is risky
  • get_content fetches any URL it is given and runs from the server's network location, which can reach internal resources
  • Browser reuse shares cookies, local storage, cache and user-agent state across requests
  • API keys stored in client config files may leak
  • Failed or timed-out fetches may return partial content or an error message
  • 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 clientsClaude Code, Codex, Gemini CLI, Claude Desktop, Cursor, OpenClaw, Antigravity, VS CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools215