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

# Connect PostHog (MCP connector)

> Connect Propane to PostHog with a personal API key—composer, Settings, scopes, and project access.

<Info>
  This guide is for the **PostHog MCP connector** (per-user session context). It is **not** an org-wide **Integration**. For Context ingestion and Signals, see [What integrations bring in](/context/integrations/what-they-bring-in).
</Info>

Propane connects to PostHog using a **personal API key** generated from your PostHog account. The setup takes about a minute.

## Where to find connectors in Propane

There are two ways to reach the connectors panel:

**From a chat session** — Click the **+** icon in the composer and select **Connectors**. A side panel opens showing every connector available in Propane. Find **PostHog** in the list to start setup.

**From Settings** — Go to **Settings → Connectors**. You will see the full list of available connectors, including **PostHog**. Click **Connect** to begin.

Both paths lead to the same setup flow. Once you have opened it, follow the steps below to generate a key in PostHog and paste it back into Propane.

<Steps>
  <Step title="Generate a key in PostHog">
    In PostHog, go to **Settings → Personal API Keys** and create a new key.

    Label it something recognisable — `propane_connector` works well. This makes the key easy to identify and revoke later if you need to.

    Choose which projects Propane can access. Under **Organization & project access**, select only the projects you want Propane to read from. We recommend scoping access narrowly rather than granting org-wide access by default.
  </Step>

  <Step title="Set scopes">
    Scopes control which kinds of data the key can read or write. Propane only needs to read from PostHog — we never write back to it — so we recommend taking the most restrictive approach that still gives Propane useful context.

    There are two ways to set scopes:

    <Tabs>
      <Tab title="Option A — Read-only, hand-picked (recommended)">
        Give the key read access to the data types you find useful for Propane to know about. Common picks include events, persons, insights, feature flags, and session recordings. Skip anything you do not want surfaced in your sessions.
      </Tab>

      <Tab title="Option B — Start from the MCP preset">
        Select PostHog's MCP server scope preset, then strip it back. Remove every write permission, and switch any data types you do not want Propane to see to **No access**. This is faster than building scopes from scratch and ends up in roughly the same place.
      </Tab>
    </Tabs>

    <Tip>
      If you are not sure which scopes to grant, start narrow. You can always edit the key later to widen access as your team gets more out of the connector.
    </Tip>
  </Step>

  <Step title="Add the key to Propane">
    Copy the generated key from PostHog, then return to the **Connectors** panel in Propane (either via the **+** in the composer or from **Settings → Connectors**). Find **PostHog** and paste the key in.

    <Check>
      That is it — Propane will start pulling context from your selected projects on your next session.
    </Check>
  </Step>
</Steps>

## Related

* [Connectors](/settings/connectors)