Skip to main content
OpenSRE connects to PostHog’s hosted Model Context Protocol (MCP) server, exposing PostHog’s products — product analytics, feature flags, error tracking, experiments, surveys, and HogQL queries — as tools the agent can call while investigating an incident. This is distinct from the PostHog bounce-rate integration, which is a narrow REST client used for watchdog alerting. Use the MCP integration when you want the agent to explore PostHog data directly.

​
Tools

ToolWhat it does
list_posthog_toolsList the tools the connected PostHog MCP server exposes
call_posthog_toolCall a named PostHog MCP tool (e.g. run a HogQL query, list feature flags, inspect an error)
The agent typically calls list_posthog_tools first to discover what is available for your project, then call_posthog_tool with the chosen tool name and arguments.

​
Prerequisites

  • A PostHog account (US or EU — the hosted server routes you automatically)
  • A PostHog personal API key created with the MCP Server preset. See PostHog’s personal API keys docs.
OpenSRE defaults to read-only access (x-posthog-read-only: true) so investigations cannot mutate your PostHog project. Set POSTHOG_MCP_READ_ONLY=false only if you explicitly want the agent to perform writes.

​
Setup

​
Option 1: Interactive CLI

opensre integrations setup
Select PostHog (MCP) when prompted, then paste your personal API key. Keep the default Streamable HTTP transport and URL unless you have a reason to change them.

​
Option 2: Environment variables

Add to your .env: 
POSTHOG_MCP_MODE=streamable-http
POSTHOG_MCP_URL=https://mcp.posthog.com/mcp
POSTHOG_MCP_AUTH_TOKEN=phx_your_personal_api_key
POSTHOG_MCP_PROJECT_ID=12345          # optional, scope to one project
POSTHOG_MCP_ORGANIZATION_ID=          # optional, scope to one organization
POSTHOG_MCP_FEATURES=                 # optional, comma-separated feature filter
POSTHOG_MCP_READ_ONLY=true            # optional, default true
VariableDefaultDescription
POSTHOG_MCP_AUTH_TOKEN—Required (hosted). Personal API key with the MCP Server preset
POSTHOG_MCP_URLhttps://mcp.posthog.com/mcpMCP server URL (use https://mcp-eu.posthog.com/mcp to pin EU)
POSTHOG_MCP_MODEstreamable-httpTransport: streamable-http, sse, or stdio
POSTHOG_MCP_PROJECT_ID—Scope tools to a specific PostHog project
POSTHOG_MCP_ORGANIZATION_ID—Scope tools to a specific organization
POSTHOG_MCP_FEATURES—Comma-separated feature filter (e.g. flags,error-tracking)
POSTHOG_MCP_READ_ONLYtrueSend the read-only header so the agent cannot mutate PostHog
POSTHOG_MCP_COMMAND—Command to launch a local MCP server (stdio mode only)
POSTHOG_MCP_ARGS—Arguments for the local MCP command (stdio mode only)
To run a local PostHog MCP server instead of the hosted endpoint, use stdio mode: 
POSTHOG_MCP_MODE=stdio
POSTHOG_MCP_COMMAND=npx
POSTHOG_MCP_ARGS=-y @posthog/mcp-server@latest
POSTHOG_MCP_AUTH_TOKEN=phx_your_personal_api_key

​
Option 3: Persistent store

{
  "version": 1,
  "integrations": [
    {
      "id": "posthog-mcp-prod",
      "service": "posthog_mcp",
      "status": "active",
      "credentials": {
        "url": "https://mcp.posthog.com/mcp",
        "mode": "streamable-http",
        "auth_token": "phx_your_personal_api_key",
        "project_id": "12345",
        "read_only": true
      }
    }
  ]
}

​
Verify

opensre integrations verify posthog_mcp
A successful check connects to the MCP server and reports how many tools it discovered. If it fails, the most common cause is a missing or invalid personal API key — confirm the key was created with the MCP Server preset and that outbound HTTPS to mcp.posthog.com is allowed.