| FMRS | 67 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 15 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 17 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Support teams using Help Scout who want AI assistants (especially Claude) to query tickets, customers, and knowledge base quickly
- Engineers who want customer context without leaving their editor or chat window
- Security-conscious teams needing read-by-default, auditable opt-in writes
| - 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 | - Teams not using Help Scout as their help desk
- Environments unwilling to grant AI access to support data
- Users expecting out-of-the-box email sending, deletes, or admin config writes (deliberately not exposed)
| - 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 | - Help Scout OAuth2 App ID and App Secret (required; authenticates as the creating user with their permissions)
- Optional: HELPSCOUT_DEFAULT_INBOX_ID to scope searches
- Optional: HELPSCOUT_DOCS_API_KEY for Docs knowledge base tools
- Optional: HELPSCOUT_ENABLE_WRITES and HELPSCOUT_ENABLE_CUSTOMER_VISIBLE_WRITES for write operations
| - 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 | - AI can access all support data (conversation content, customer and organization info); credential leakage risks data exposure
- Message content is included by default; REDACT_MESSAGE_CONTENT is not a compliance boundary and does not remove all customer identifiers
- When writes are enabled, the server can modify conversation status, tags, assignments, etc.; tier-2 operations (sendReply/publishDraft) email customers and require care despite confirmation mechanisms
- Help Scout OAuth2 has no separate scope selection; the app acts with the creator's permissions, so shared credentials widen impact
| - 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, Claude Code, Cursor, VS Code, Windsurf, Continue.dev, Goose, Claude Cowork, Codex, Gemini CLI, OpenCode | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 4 | 26 | 11 |
|---|