Name: PostHog MCP
Author: PostHog

LABSCO SUMMARY

Free to connect, and very wide once you are in.

Connecting and calling tools costs nothing; normal PostHog usage billing still applies to the data behind your queries, and the tools that run an LLM internally bill as PostHog AI spend and only appear when AI data processing is enabled for the organisation. Because it writes as well as reads, the levers worth setting up front are read-only mode, tool filtering by name or category, and pinning the session to one organisation or project.

What it is

PostHog's free hosted MCP endpoint at https://mcp.posthog.com/mcp. It exposes PostHog's products as function-calling tools to any MCP-compatible client, and routes to the US or EU region based on the account you sign in with.

What you get

Feature flags, experiments and surveys created, launched and updated from a prompt
Error tracking: issue lists, a single issue with its events, merges, splits and assignment rules
SQL run against your project, plus insights, dashboards and web analytics queries
Logs queried, counted, pattern-mined and diffed between two time windows
Session recordings, playlists, CDP destinations and data warehouse sources
Stable tool names, so a tools query parameter can scope a session to a subset
npx @posthog/wizard mcp add installs it into PostHog Desktop, Cursor, Claude Code, Claude Desktop, Codex, VS Code and Zed

Requirements

A PostHog account. OAuth is the default path and needs no key; a client that cannot do OAuth uses a personal API key created with the MCP Server preset, sent as an Authorization: Bearer header. Enterprise plans can route access through an identity provider instead of per-user keys.

Setup effort

One command plus a key — npx @posthog/wizard@latest mcp add, then supply credentials

See installation options

USE CASES

01

Triaging this week's errors from inside the editor

Rank the issues by occurrence, open the one that matters with its events and stack trace, then propose the fix in the same conversation.

02

Closing the loop on an issue you just fixed

Update the issue state and add an assignment rule so the next occurrence of that class lands on the right team automatically.

03

Shipping a feature flag from a prompt

Create the flag, check its definition and evaluation reasons, and see which flags depend on it before you roll it out.

04

Answering a product question with SQL

Write the query in conversation and run it against your project, instead of switching to the PostHog UI to paste it in.

05

Chasing a spike in the logs

Scan a service for volume anomalies, mine the patterns behind them, and diff those patterns against an earlier window.

06

Running an experiment end to end

Create it, work out the running time it needs, launch it, and end it — without leaving the editor between steps.

2 tools

Listed in project docs. Your client may show a different list.

exec

render-ui

BEFORE YOU INSTALL

What to know first

Tools you get

2 tools named in the project's documentation.

INSTALLATION

Connect your client

Server setup

npx

Claude Desktop, Claude Code, VS Code, Zed

TERMINAL

npx @posthog/wizard@latest mcp add

Hosted endpoint

ENDPOINT URL

https://mcp.posthog.com/mcp

Add this hosted endpoint to your MCP client using the credentials listed under Requirements.

MCP Clients

Cursor

CURSOR · JSON

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

PostHog MCP