Start free →

PostHog

Connecting PostHog lets an agent check whether a feature it shipped is actually being used, and whether a change moved the numbers you expected.

Before you start

You need a PostHog personal API key. Create one from your user settings in PostHog, under personal API keys, and give it read access to the project you want agents to query. PostHog's own guide is Model Context Protocol.

Copy the key when it is shown. PostHog will not show it again.

Connect it

  1. In SetForth, open your project, then Integrations.
  2. Choose PostHog.
  3. Leave the server URL as https://mcp.posthog.com/mcp unless PostHog gave you a different one.
  4. Paste the personal API key.
  5. Choose Connect. SetForth tests the connection and reports the result.

If your data lives in PostHog's EU cloud or your own instance, use the server URL for that instance instead.

What agents can check

Connecting a product analytics tool adds three follow-ups:

  • Verify event tracking confirms the events a task promised to emit actually fire in production. You name the events and how long to watch for.
  • Measure feature adoption reports how many people touched the new surface, and fails when unique users stay below the minimum you set. A feature nobody uses is a result worth knowing, and the agent gets it back rather than closing the task.
  • No metric regression flags a task when a funnel step drops against its pre-release baseline by more than the tolerance you allow.

You set the window, the thresholds, and which events or funnel to watch when you add the follow-up during planning.