| FMRS | 44 / 100 · D | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 4 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 6 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 11 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 8 / 20 | 17 / 20 | 16 / 20 |
|---|
| Best for | - Users who already run multiple CLI coding agents (Claude Code, Codex, Gemini CLI, etc.) and want one unified interface
- Individuals or teams wanting local-only storage (SQLite) and control over which LLM API key/provider they use
- Users who need scheduled automation or multi-channel remote access to an AI agent
| - 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 | - Use cases needing a lightweight, single-purpose MCP tool server
- Users wanting a fully managed cloud service with no local install
- Scenarios requiring an officially Anthropic- or protocol-maintained MCP server
| - 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 | - Local file system read/write access for agent file operations
- Ability to execute locally installed CLI agents
- Network access to call configured LLM provider APIs
- Optional bot tokens and network access for chat-platform integrations (Telegram, Lark, DingTalk, WeChat)
- Local SQLite database storage
| - 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 | - Agents get broad local file read/write and command-execution access, which requires trust before enabling
- "YOLO Mode" and "Full-Auto Mode" auto-approve agent actions without confirmation, raising the risk of unintended file changes if misconfigured
- Chat-platform integrations require storing bot tokens/credentials, which carries credential-exposure risk if mishandled
- The project is maintained by a single company (iOfficeAI); evaluate its security practices and update cadence before granting broad automation permissions
| - 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 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 |
|---|