Connect PostHog with Unblocked to give AI agents product analytics context

PostHog records how people use your product and how your team measures and improves that experience. Unblocked makes selected PostHog projects usable as cited context when an AI agent or developer needs to understand product behavior, an experiment, a survey result, or the rollout state of a feature.

PostHog context is reconciled with your code, pull requests, issues, incidents, and docs. This lets an agent connect a product signal—such as an onboarding drop-off or a change in feature adoption—to the implementation and engineering history behind it.

Once connected, any MCP-compatible coding agent—including Claude Code, Cursor, Windsurf, GitHub Copilot, and Codex—can research this context through one Unblocked MCP server connection. Unblocked is the MCP context layer; agents do not connect directly to PostHog.

What you get

• Dashboards and notebooks — Give agents the definitions, analysis, and product context your team already uses to understand performance.
• Surveys — Bring customer feedback into engineering research alongside related code, issues, and documentation.
• Experiments — Connect experiment context to the code and pull requests that implement the tested experience.
• Feature flags — Help agents understand rollout context and relate a feature flag to the code paths and changes behind it.
• Project scoping — Select the PostHog organization and projects Unblocked should reference.
• Cited source links — Answers link back to the original PostHog resource so developers can verify the source.
• Cross-source synthesis — Combine PostHog product analytics context with code, pull requests, issues, incidents, documentation, and conversations in one knowledge graph.
• Permission-aware answers — When Data Shield is enabled for PostHog, Unblocked respects each user's access to PostHog projects and resources.

Need screenshots or troubleshooting?This is a concise connection summary. Follow the complete setup guide ↗

Prerequisites

• An Unblocked account on a paid plan.
• Team admin access in Unblocked.
• A PostHog Cloud account in the US or EU region with access to the organization and projects you want to connect.
• An MCP-compatible coding agent such as Claude Code, Cursor, Windsurf, GitHub Copilot, Codex, OpenCode, or VS Code to use the context in your editor.

Step 1: Connect PostHog to Unblocked

1. In Unblocked, go to Settings → Data Sources → Connect another data source.
2. Under Data & Analytics, select PostHog.
3. Sign in to PostHog and authorize Unblocked using OAuth. You do not need to create or copy an API key.
4. Select the PostHog organization and projects that Unblocked should reference.
5. Click Save Settings. Unblocked begins ingesting dashboards, notebooks, surveys, experiments, and feature flags from the selected projects.

You can later change project access under Settings → Data Sources → PostHog. To include future projects automatically, open Manage Preferences and enable Automatically include newly created projects.

Step 2: Install the Unblocked MCP server

On macOS or Linux, one command auto-detects and configures your supported agents (Claude Code, Cursor, Windsurf, GitHub Copilot, Codex, OpenCode, VS Code):

On Windows, or when you prefer remote MCP, add the server manually using the configuration below, or follow the manual install guide ↗.

claude mcp add -s user --transport http unblocked https://getunblocked.com/api/mcpsse

{
  "mcpServers": {
    "unblocked": {
      "url": "https://getunblocked.com/api/mcpsse"
    }
  }
}

https://getunblocked.com/api/mcpsse

To give Claude Code, Cursor, GitHub Copilot, Codex, or another MCP-compatible AI coding agent access to PostHog context, connect PostHog to Unblocked and add the single Unblocked MCP server to your agent.

Unblocked acts as the MCP context layer for your PostHog data, searching dashboards, notebooks, surveys, experiments, feature flags alongside your other connected sources and returning cited results through these tools:

• context_researchResearches a focused question across PostHog resources, code, pull requests, issues, incidents, docs, and conversations, then returns a synthesized answer with source citations.
• context_get_urlsFetches the full content behind a supported PostHog resource URL that an agent encounters, with links back to the original source.
• research_taskInvestigates a broader product or engineering question across PostHog and your connected development tools, producing a research brief when you do not know which source to start from.

Questions you (or your agent) can ask Unblocked about your PostHog data:

• Where are users dropping out of onboarding?
• Which platforms account for the onboarding drop-off, and what code handles that step?
• How many users are affected by this drop-off?
• Were there relevant pull requests or incidents during that period?
• How has activation changed this quarter?
• Is adoption of the new editor increasing week over week?
• How did usage change after July 15?
• How does our PostHog dashboard define activation?
• Which experiment or feature flag controls this experience, and where is it implemented?