PostHog MCP Server

The PostHog MCP server is a provider-hosted remote server that lets AI agents interact directly with a PostHog workspace. It exposes the full PostHog API surface as MCP tools, covering product analytics (trends, funnels, retention, paths, lifecycle, stickiness), feature flags, A/B experiments, cohorts, dashboards, insights, surveys, annotations, alerts, persons, error tracking, logs, notebooks, session replays, web analytics, data warehouse sources, and HogQL/SQL execution.

The server lives at https://mcp.posthog.com/mcp and automatically routes to the correct data region (US or EU) based on the authenticated user. Authentication uses OAuth2 for supported clients (Cursor, Claude, VS Code, Zed, etc.) or a personal API key via a Bearer token header for clients without OAuth. Tools can be filtered per request using ?features= (feature categories like flags,dashboards,insights) or ?tools= (explicit tool names), and access can be pinned to a specific organization or project via x-posthog-organization-id and x-posthog-project-id headers.

The server is free to use, connection and tool invocations do not incur PostHog billing charges, and queries execute directly against the PostHog project without intermediate storage. The original standalone repo at github.com/PostHog/mcp has been archived and folded into the main PostHog monorepo under services/mcp.

Tools

Prerequisites

• A PostHog account (Cloud US or Cloud EU).
• For API key auth: a personal API key created in PostHog with the "MCP Server" scope preset.

Quick install (recommended)

The PostHog wizard auto-configures the MCP server for Cursor, Claude Code, Claude Desktop, Codex, VS Code, Windsurf, and Zed:

npx @posthog/wizard@latest mcp add

Manual config (OAuth)

Most MCP clients can connect directly to the remote URL and complete an OAuth flow on first use:

{
  "mcpServers": {
    "posthog": {
      "url": "https://mcp.posthog.com/mcp"
    }
  }
}

Manual config (API key)

For clients without OAuth support, pass a personal API key as a Bearer token:

{
  "mcpServers": {
    "posthog": {
      "url": "https://mcp.posthog.com/mcp",
      "headers": {
        "Authorization": "Bearer phx_your_api_key_here"
      }
    }
  }
}

Optional: pin to an org/project or filter tools

Append query params to filter tools, or add headers to pin scope:

https://mcp.posthog.com/mcp?features=flags,dashboards,insights
https://mcp.posthog.com/mcp?tools=dashboard-get,feature-flag-get-all,execute-sql

Headers:

• x-posthog-organization-id: pin to a specific organization
• x-posthog-project-id: pin to a specific project

• Ask an agent to build and run trends, funnel, retention, or path queries over your event data and return results inline, without writing HogQL by hand.
• Create, update, and roll out feature flags (including multivariate variants and scheduled changes) directly from Cursor or Claude during a code change.
• Spin up A/B experiments from a PR description, then check on results and end the experiment when the winning variant is decided.
• Investigate production issues by combining error tracking, log queries, and session replay tools to find the affected users and root cause.
• Build cohorts (dynamic or static), create surveys targeted at those cohorts, then pull response stats back into the conversation.

• "How many unique users signed up in the last 7 days, broken down by day?"
• "Create a feature flag called new-checkout-flow rolled out to 20% of users."
• "Create a multivariate flag homepage-hero-test with control 34%, variant_a 33%, variant_b 33%, and launch an experiment measuring conversion to checkout."
• "What are the top 5 error tracking issues this week, and which release introduced the most affected one?"
• "Build a dynamic cohort called power-users for anyone who completed a purchase more than 5 times in the last 30 days, then create a survey targeting them."

• Officially built and hosted by PostHog, with no self-hosting or container required.
• Very broad coverage across product analytics, feature flags, experiments, cohorts, dashboards, surveys, error tracking, logs, and HogQL/SQL.
• Supports OAuth in addition to personal API keys, with org/project pinning and tool-level filtering via query params.
• Auto-routes to US or EU PostHog regions and is free to use (no extra billing for MCP calls).

• The full tool surface is very large (hundreds of tools across categories), which can overwhelm an agent's context unless filtered with ?features= or ?tools=.
• Some clients without remote MCP or OAuth support require manual Bearer token configuration with a personal API key.
• The historical standalone repo (PostHog/mcp) is archived; source now lives inside the PostHog monorepo, which is less convenient to browse.

• Google Analytics MCP for GA4 reporting in place of PostHog product analytics.
• Amplitude MCP server for teams on Amplitude instead of PostHog.
• Statsig MCP server for feature flag and experimentation workflows specifically.