PostHog MCP server

PostHog × Cursor

Use the PostHog MCP server
in Cursor

Query analytics, insights, and feature flags in PostHog. This guide connects PostHog to Cursor (the AI code editor) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · OAuth sign-in

Setup: PostHog in Cursor

Cursor adds MCP servers via MCP settings or install deep links. The gateway route takes about two minutes:

  1. Connect PostHog to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to Cursor' — Cursor opens and asks to install the gateway.
  3. Confirm and approve the sign-in.
  4. PostHog's tools are now available to Cursor's agent, governed by your rules.

What to ask once it’s connected

How did signups trend this week?
Which feature flags are currently active?
Show the funnel from landing page to signup.
Which pages convert best?

Why route it through a gateway

One URL, every client

The same PostHog connection works in Claude, Claude Code, ChatGPT, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool PostHog exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Cursor did with PostHog — searchable, exportable, auditable.

Scanned and probed

PostHog passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: PostHog in Claude · PostHog in Claude Code · PostHog in ChatGPT · PostHog in VS Code