PostHog
Give the Sazabi agent tools to query analytics data, feature flags, and experiment results from your PostHog organization.
About
PostHog is an MCP connector that gives the Sazabi agent tools to query analytics data, feature flags, and experiment results. PostHog's MCP server authenticates via OAuth with dynamic client registration. Once connected, agents can query event analytics, inspect feature flag configurations, and review experiment results. This connector grants read and write access, enabling agents to create and update feature flags, insights, dashboards, and experiments on your behalf.
What the agent can do:
- Query product analytics events and trends
- Browse and manage feature flag configurations and rollout status
- Review A/B test and experiment results
- Search person and group properties
Prerequisites
- A PostHog account
- Permission to authorize third-party OAuth applications in PostHog
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find PostHog in Settings > MCP connectors.
Authorize
Start the connection; Sazabi redirects you to PostHog to authorize, then back.
Set up with the CLI
You can also connect PostHog with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).
PostHog authenticates over OAuth, so the CLI opens a browser to complete authorization:
sazabi mcp-connectors connect posthogAdd --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized (OAuth) or the key/header is correct (token auth).
Troubleshooting
No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.
Connection shows needs attention — The authorization or key may have expired or been revoked; reconnect from Settings > MCP connectors.