| FMRS | 46 / 100 · D | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 4 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 9 / 20 | 17 / 20 | 16 / 20 |
|---|
| Best for | - Users who need Claude Code, OpenClaw, Cursor, or Windsurf to access content across multiple platforms
- Individuals and developers seeking free or open-source upstream tools for web research
- Agent workflows that need centralized installation, diagnostics, and backend routing
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
| - Q&A and research scenarios that need real-time, clean web content
- Users with an existing Exa account who want a zero-deployment remote option
|
|---|
| Not for | - Tasks requiring graphical browser interaction, form submission, or automated login
- Deployments requiring a standalone MCP server or a documented MCP transport
- Environments that do not allow shell command execution by the agent
- Use cases requiring every platform to work without login state or cookies
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
| - Scenarios requiring a strict allowlist of search sources that can't use a third-party search service
- Budget-sensitive, high-volume search scenarios (remote/API calls may incur cost)
|
|---|
| Required permissions | - The agent must execute shell commands, including pip install, system dependency installation, and upstream CLI calls
- Some channels require local browser login state, cookies, or tokens
- Credentials are stored locally in ~/.agent-reach/config.yaml; the README states the file mode is 600
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
| - Requires an Exa API key for full functionality; OAuth login is optional in remote mode
- web_fetch_exa retrieves content from a specified URL; agent_run performs multi-step autonomous actions and needs the user to have clear expectations of Agent behavior
|
|---|
| Risks and side effects | - Cookie- or login-state-based access to Twitter/X, Xiaohongshu, Reddit, and similar platforms may trigger detection, restrictions, or account bans
- The default installation may install Node.js, gh CLI, mcporter, and other system infrastructure, and modify agent skills and MCP configuration
- Platform anti-crawling changes or upstream tool changes may break individual channels
- Server deployments may require a proxy; the README estimates roughly $1 per month
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
| - The API key should be stored carefully — avoid leaving it in plaintext in client config files on untrusted machines
- agent_run is a multi-step autonomous tool with a longer action chain — try it on low-risk tasks first
|
|---|
| Supported clients | Claude Code, OpenClaw, Cursor, Windsurf | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, Antigravity |
|---|
| Tools | 0 | 11 | 4 |
|---|