| FMRS | 46 / 100 · D | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 9 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 11 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 9 / 20 | 17 / 20 | 16 / 20 |
|---|
| Best for | - Individuals or developers who want to search, compare, and book flights and hotels conversationally through an agent
- Agent workflows willing to complete a one-time, zero-amount card verification in exchange for free flight search and booking
- Travel booking flows that specifically need free-cancellation, pay-later hotel options
| - 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 | - High-volume, commercial-scale integrations wanting prepaid-credit billing (use the separate paid Developer API instead)
- Users unwilling to keep any payment method on file, since hotel functionality mandates a saved card for every call
- Use cases requiring guaranteed (non free-cancellation) hotel rates, since only pay-later-eligible rates are sold
| - 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 | - Network access to letsfg.co's cloud search and booking engine
- A saved payment method / card on file via `letsfg auth` (a zero-amount Stripe setup used to issue a 90-day Bearer token)
- For hotel tools, a valid saved payment method required on every call, including search
- Optional LETSFG_API_KEY secret environment variable, needed only for the paid Developer API path
| - 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 | - Hotel search and booking both mandate a saved, valid card on file for every call — unusual compared to typical free search tools and worth surfacing to users before use
- Hotel bookings charge a 10% non-refundable reservation fee that is not returned even if the booking is later cancelled
- Hotel booking is asynchronous, returning a booking_job_id rather than a confirmation; retrying book_hotel blindly for the same rate can double-book the room and double-charge the reservation fee
- The README explicitly warns against accidentally calling `letsfg register` / `letsfg setup-payment`, which creates a separate paid commercial billing account not intended for the normal agent flow
- The repository's license field is listed as NOASSERTION while the README claims an MIT license, leaving the actual licensing status somewhat unclear
| - 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, 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 | 5 | 11 | 4 |
|---|