| FMRS | 41 / 100 · D | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 4 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 17 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 7 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 5 / 20 | 17 / 20 | 16 / 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
| - 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 | - 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
| - 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 | - 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 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 | - 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
| - 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, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, Antigravity |
|---|
| Tools | 0 | 11 | 4 |
|---|