| FMRS | 73 / 100 · B | 75 / 100 · B | 70 / 100 · B |
|---|
| Verification | Source and config reviewed | Source and config reviewed | Source and config reviewed |
|---|
| Reliability | 12 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 13 / 20 | 12 / 20 | 15 / 20 |
|---|
| Maintenance | 16 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 | 15 / 20 |
|---|
| Setup experience | 16 / 20 | 17 / 20 | 12 / 20 |
|---|
| Best for | - 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
| - 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
| - Developers and operators who want AI assistance across the whole AWS containerization deployment flow
- Scenarios that need to quickly root-cause an ECS deployment issue
|
|---|
| Not for | - 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)
| - 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)
| - Teams without an AWS account or not using ECS
- Teams highly cautious about automated production deployments that don't want an AI directly creating cloud resources (keep ALLOW_WRITE=false for read-only troubleshooting)
|
|---|
| Required permissions | - 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
| - 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 valid AWS credentials (an AWS CLI profile); actual scope depends on what that IAM identity is granted
- With ALLOW_WRITE=true it can create/modify/delete ECS services, ECR repos, and other cloud resources; ALLOW_SENSITIVE_DATA gates access to logs and other sensitive data
|
|---|
| Risks and side effects | - 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
| - 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
| - With write access enabled, the assistant's actions can directly incur cloud costs or accidentally delete production resources — test in a non-production account or with an approval workflow first
- delete_app removes all resources created by an Express Mode deployment and is irreversible — confirm the target application carefully
|
|---|
| Supported clients | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Kiro, Cline |
|---|
| Tools | 4 | 11 | 7 |
|---|