| FMRS | 41 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 4 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 17 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 7 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 5 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Teams already using PostHog for product analytics, feature flags, or experiments who want to control it from an AI agent
- Developers who want product signals (errors, rage clicks, etc.) surfaced directly inside Claude Code, Cursor, or similar agent environments
| - 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 who only need a narrow, single-purpose MCP tool (e.g., pure database or file-system access) — PostHog's surface area is broad
- Users requiring a strictly FOSS codebase — the `ee` directory in this repo is under a separate, non-MIT license
- Self-hosted deployments needing vendor support — the README explicitly states no customer support or guarantees are provided for open-source deployments
| - 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 | - Access to data within a PostHog project/account, including events, session recordings, feature flags, experiments, error tracking, surveys, and data warehouse records
- Write access to modify project configuration if using the agent to create or change feature flags/experiments
| - 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 | - PostHog aggregates substantial user behavioral and product data; agent access to it carries exposure risk for sensitive information (user identifiers, session content)
- Repository licensing is mixed (MIT for the main repo, separate proprietary license for the `ee` directory) — confirm which features are covered before relying on them in production
- Self-hosted open-source deployments are explicitly unsupported by the vendor and are recommended only up to roughly 100k events/month before needing to migrate to Cloud
| - 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, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|