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.

DimensionCRW Web ScraperOpen-source web scraping MCP server for AI agents with scrape, crawl, and map capabilitiesGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS54 / 100 · D76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions11 / 2014 / 20
Maintenance12 / 2018 / 20
Documentation10 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Teams that want self-hosted web scraping with data control
  • Developers using Claude Code, Cursor, Codex, Gemini CLI, OpenCode, or Windsurf
  • Scenarios needing a low-resource single Rust binary
  • Migration projects requiring a Firecrawl-compatible REST API
  • 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 need official Firecrawl, Tavily, or Anthropic backing or support
  • Scraping needs that will not respect site policies and robots.txt
  • Teams needing a fully managed SaaS without deploying anything themselves
  • 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
  • Network access: outbound HTTP/HTTPS requests to scrape, crawl, and search the web
  • Local filesystem read/write: to store configuration such as ~/.config/crw/config.toml
  • The install script may modify MCP configuration of detected AI tools
  • A CRW_API_KEY credential is required when using the managed cloud
  • 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
  • Scraping third-party sites may conflict with their terms of service, copyright, or robots.txt rules; the project states crawl and map follow robots.txt by default
  • The one-command install downloads and executes a remote script, which carries supply-chain risk
  • The API key is stored in ~/.config/crw/config.toml, so local file permissions and leakage matter
  • The container image uses the latest tag, which may make versions non-reproducible
  • Managed cloud and local capabilities or response shapes can differ; check /v1/capabilities and response shapes before migrating
  • 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 Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools015