PostHog MCP server

officialstreamable_httplocalofficialhealthy

Query PostHog analytics, manage flags, and triage errors from your AI agent

Official PostHog MCP Server 🦔

Featured profile Is it safe?Setup guide Alternatives Claim this server

00About

The official PostHog MCP server is a free, hosted endpoint that lets an MCP-compatible agent read and write across PostHog's products from plain-text prompts. Agents can run analytics and HogQL queries, manage feature flags and experiments, triage errors, set up CDP destinations, and chain multi-step workflows.

Hosted remote endpoint

Connect any MCP-compatible client to https://mcp.posthog.com/mcp. The PostHog authentication server automatically routes you to the correct data region (US or EU) based on the account you log in with.

Read and write across PostHog

Once connected, the agent can run analytics queries, manage feature flags and experiments, execute SQL, configure CDP destinations, and triage support tickets, plus multi-step recipes that chain these together.

Error triage in your editor

Ask for the top errors in a project this week, pull a full stack trace and metadata to propose a fix, or mark an issue resolved and create an assignment rule.

Governed metrics from your semantic layer

Run governed metrics from your semantic layer (beta) so every agent session answers questions like "what's our MRR?" with the same canonical definition.

Wide client support

Works with PostHog Desktop, Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf, and Zed. The PostHog Wizard (npx @posthog/wizard mcp add) can install it directly into several of these.

Who it’s for. Product and engineering teams already using PostHog who want to query analytics, manage feature flags, and debug errors from Claude Code, Cursor, or another MCP client without switching to the browser.

Example prompts

Rank recent errors

What are the top 5 errors in my project this week? Return error groups ranked by occurrence with affected user counts.

Trace and fix a crash

Show me the full stack trace for the most recent crash, then propose a fix based on the error message and metadata.

Resolve and route issues

Mark this issue as resolved and assign all future TypeErrors to the backend team.

Run a HogQL query

Run a HogQL query to get daily signups for the last 30 days and summarize the trend.

auth: OAuth · pricing: Connecting and calling MCP tools is free; some AI-powered tools bill as PostHog AI spend · auto-generated from the project's README, site, and live tools list; not yet reviewed

01Tools · 0

Tools require a live tools/list handshake. For local/stdio servers that runs in a sandbox (gated off until configured); remote servers are probed directly.

02Install & source

https://mcp.posthog.com/mcp

remote_url

repohttps://github.com/PostHog/posthog
homepagehttps://posthog.com/docs/model-context-protocol
licenseNOASSERTION
adoption39875 stars · 3406 forks

05Provenance & freshness

sourcesUser submissions [p7]

last_checked2026-09-20 20:33Z

next_check2026-09-20 23:33Z

cadenceevery 3h

verifiedmetadata:passed handshake:skipped metadata:passed handshake:skipped metadata:passed handshake:skipped metadata:passed handshake:skipped metadata:passed handshake:skipped

index_statusindex — 7 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README.

[![PostHog MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/posthog.svg)](https://mcpexplorer.com/servers/posthog)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →