| FMRS | 62 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Users of Gemini CLI, Gemini Code Assist, or Claude Code who want to query Google Analytics data in natural language
- Analysts with a Google Cloud project and Google Analytics access who can configure ADC credentials
- Teams that prefer running the server locally and managing their own credentials
| - 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 | - Users without Google Analytics access or the ability to configure Google Cloud credentials
- Users looking for a fully managed, zero-configuration service
- Scenarios that need to write to or modify Google Analytics configuration (the credential scope is read-only)
- Production scenarios with strict stability requirements, given the experimental status
| - 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 | - Application Default Credentials for a user with access to the target Google Analytics accounts or properties
- Google Analytics read-only scope https://www.googleapis.com/auth/analytics.readonly
- Google Analytics Admin API and Google Analytics Data API enabled in the Google Cloud project
- Optional Google Cloud project ID (GOOGLE_PROJECT_ID) for quota and billing attribution
| - 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 | - The server is experimental, so behavior and interfaces may change
- Credentials are stored locally as a JSON file referenced by an environment variable; if exposed, Google Analytics data could be read
- Queries are generated by an LLM and may produce inaccurate or unintended reporting requests
- Network access to the Google Analytics APIs is required
| - 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 | Gemini CLI, Gemini Code Assist, Claude Code | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 7 | 26 | 11 |
|---|