> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PostHog

> Give the Sazabi agent tools to query analytics data, feature flags, and experiment results from your PostHog organization.

[All PostHog integration capabilities](https://docs.sazabi.com/catalogs/integrations/posthog)

## 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**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find PostHog in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### 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](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)).

PostHog authenticates over OAuth, so the CLI opens a browser to complete authorization:

```bash theme={"system"}
sazabi mcp-connectors connect posthog
```

Add `--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**](https://app.sazabi.com/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**](https://app.sazabi.com/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**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.