Google's free service for monitoring your own site's indexing and Google Search queries, clicks and impressions. Its official API supports reporting and site/sitemap operations; a separate daily export can send performance data to BigQuery.
PostHog
Product analyticsIndependent review. Unpaid; no partnership with PostHog. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Product analytics, session replay, feature flags, experiments and a data warehouse in one place, with an official MCP server so agents can query product data directly.
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
- Value
- Product analytics, session replay, feature flags, experiments and a data warehouse in one place, with an official MCP server so agents can query product data directly.
- Differentiation
- Documented fit: Product and growth teams that want analytics, replays and flags together; Asking product-usage questions from an AI agent or editor. Uniqueness is not established.
- Replaceability and switching
- Compare Google Search Console. Not drop-in replacements. Export completeness and migration effort remain unverified.
- Ease and technical aptitude
- Consider the fit limits: Using PostHog's AI-powered MCP tools without enabling AI data processing (they require it). Setup effort has not been scored.
- Interoperability and portability
- See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
Connections: MCP connections · APIs · Portability and vendor lock-in.
- Product and growth teams that want analytics, replays and flags together
- Asking product-usage questions from an AI agent or editor
- Using PostHog's AI-powered MCP tools without enabling AI data processing (they require it)
Top use cases
- Track funnels and retention with product analytics source ↗
- Watch session replays to see where users get stuck source ↗
- Roll out features gradually with feature flags source ↗
- Run A/B tests with experiments source ↗
- Query product data from Claude Code, Codex or Cursor through the MCP server source ↗
In depth
One place for product data
The warehouse can combine product data with connected business sources and uploaded CSV, JSON or Parquet files. Connector availability and supported tables vary by source; check the specific source’s guide before relying on it. source ↗
Agent access
PostHog runs a hosted MCP server that works with any MCP-compatible client. Its docs name Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed, and say connecting and calling tools is free while some tools use LLM credits. source ↗
Free tier
Monthly free allowances include one million analytics events, 5,000 session replays and one million feature-flag requests. Paid usage is metered by product in USD, excluding tax. At a free or configured billing limit, new events can be permanently dropped and feature flags return a quota-limited default response. Checked 2026-10-18. source ↗
MCP costs
Connecting to the PostHog MCP server and calling its tools is free, but some tools use LLMs internally and may be billed as PostHog AI spend; those are available only when AI data processing is enabled. source ↗
Experiments over MCP
PostHog's MCP server lets an agent estimate sample size and running time, create an experiment with its feature flag, launch, pause or end it, read results and ship a winning variant. Shipping changes what users see, so keep a person on that step. Checked 2026-10-18. source ↗
How to use it with AI
How PostHog connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Claude Code and Claude Desktop setup guides. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. PostHog named integration docs ↗PostHog MCP / connector evidence ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands PostHog publishes an API, but this pairing still needs network, authentication and execution-scope checks. PostHog API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). PostHog is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. PostHog's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. PostHog file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Named as a supported client. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. PostHog named integration docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces PostHog publishes an API, but this pairing still needs network, authentication and execution-scope checks. PostHog API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. PostHog is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. PostHog's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. PostHog file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented PostHog has an official MCP server and Google Antigravity supports MCP, but PostHog's docs don't name this pairing. Auth setup may differ. PostHog MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks PostHog publishes an API, but this pairing still needs network, authentication and execution-scope checks. PostHog API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. PostHog is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. PostHog's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. PostHog file docs ↗Google Antigravity file docs ↗ |
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
Agent compatibility
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ (available to all users; private reads/writes require scoped authentication and the correct US/EU endpoint) |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | Yes | Official docs ↗ (CSV, JSON or Parquet files up to 50 MB; static uploads do not automatically refresh) |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
Appears in these proposed stacks
Business data & reporting Product data
Dev, web & IT Swap-in
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Workflows using this tool
- Write a monthly SEO and product report
- Ask product analytics questions from your editor
- Run an A/B test with an AI pair
- Analyze an export by chatting with it
- Build a quiz funnel and A/B test each question with PostHog
- Send agent-drafted letters through a mail API, with approval
Explained in the wiki
Review
No long-form review yet. Verdict is based on research, not hands-on testing.