| FMRS | 46 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 11 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 9 / 20 | 15 / 20 | 17 / 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
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
| - 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
|
|---|
| 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
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
| - 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)
|
|---|
| 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 HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
| - 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
|
|---|
| 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
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
| - 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
|
|---|
| Supported clients | Claude Desktop, Cursor, Windsurf | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 5 | 26 | 11 |
|---|