Skip to main content
PostHog via MCP gives Corunner agents a read-only interface for product analytics and insights. This page covers how to connect PostHog, configure usage guidance, verify capabilities, and manage the connection in Corunner.

Connect with PostHog

Open the MCP Servers tab in the Corunner web app.

​
Server details

PostHog Cloud is the single profile available and is prefilled automatically when Corunner manages the endpoint.

​
Connect PostHog

1

Sign in

Sign in to Corunner at app.corunner.ai.
2

Open Integrations

Open Integrations in the left sidebar.
3

Select MCP Servers

Select the MCP Servers tab.
4

Find the PostHog card

Find the PostHog card in the grid.
5

Turn on the Connect toggle

Turn on the Connect toggle. The Connect PostHog modal opens.
6

Verify the Server name

Verify the prefilled Server name (“PostHog” by default; rename if you run multiple instances).
7

Verify the Server URL

Verify the prefilled Server URL. Value: https://mcp.posthog.com/mcp. If Corunner manages the endpoint, the field shows a “Managed by Corunner” hint and is read-only.
8

Click Test URL

Click Test URL to confirm the endpoint format is valid and the server responds.
9

Select authentication

Select the authentication method (prefilled OAuth).
10

Open Advanced (optional)

Optionally click Advanced to expand custom headers and Usage guidance.
11

Enter Usage guidance

Enter Usage guidance describing when and how agents should use this server (see the next section for a copyable example).
12

Click Connect with PostHog

Click Connect with PostHog (OAuth).
13

Authorize with PostHog

Corunner redirects the current tab to the provider’s authorization page.
14

Approve permissions

Review and approve the requested permissions in the provider consent screen.
15

Return to Corunner

After approval, return to Corunner automatically.
16

Confirm Connected

Confirm a green Connected badge and an enabled Connected toggle on the PostHog card.

​
Configure Usage Guidance

Usage guidance tells Corunner agents when and how to use this server. It is optional but recommended for safe, consistent behavior. Good guidance answers six purposes:
  • When should agents use this server?
  • What specific tasks should they perform?
  • Which tasks are permitted?
  • Which tasks require human approval?
  • What must not be accessed?
  • How should results be presented?
Never enter secrets into Usage guidance. This field is for instructions, not credentials.
Copy and adapt this example:

​
Verify the Connection

After a successful connection, the PostHog card shows:
  • a green Connected status pill on the name row
  • an enabled Connected toggle
  • a meta line such as Connected to <workspace> with a relative time
  • a <N> capabilities button that expands into the capability list

​
Capabilities

PostHog exposes the following capabilities to Corunner agents:
  • query trends and funnels
  • inspect retention and paths
  • read flags and experiments
  • review dashboards and cohorts
  • read-only beta
PostHog MCP is in read-only beta; the specific tools change as PostHog evolves the server. Click the capability count on the connected card to see the current tools.

​
Check Connection Health

On the connected card, the Test connection icon (Wi-Fi glyph next to the Connected toggle) runs a live probe of the server.
  • Green check = reachable and credentials valid
  • Red warning = probe failed
If the test fails, open Edit configuration to refresh credentials or update the Server URL.

​
Edit Configuration

Click the Edit configuration icon (settings glyph) on the connected card to update the connection. Editable fields:
  • Server name
  • Server URL (only if not managed by Corunner for this server)
  • Authentication method and credentials
  • Custom headers (non-OAuth only, under Advanced)
  • Usage guidance
Creating, editing, disconnecting, and changing observation consent are admin-only actions. Members can view status and capabilities but cannot modify the connection.
Click the Observation consent icon (brain glyph) on the connected card to open the Observation consent - PostHog drawer. Observation is separate from tool connection. It controls whether Corunner passively reads resources into organizational memory, while capabilities are unaffected. Scopes have Mode (Disabled / Shadow / Active) and Sensitivity (Standard / Restricted / Excluded). Excluded scopes cannot be enabled.
“Observation is separate from connecting a tool. Only resources listed here are eligible for passive intelligence, and excluded scopes cannot be enabled.”
The precise effect on Memory & Learnings for advanced modes should be confirmed with the Corunner product team if you plan to depend on it in policy.
Creating, editing, disconnecting, and changing observation consent are admin-only.

​
Disable or Disconnect

Disconnecting deletes stored credentials for this connection. Provider-side OAuth tokens should also be revoked from the provider account if you want to eliminate them entirely.

​
Connect PostHog

Connect with PostHog

Ready to go? Open the MCP Servers tab and turn on the PostHog Connect toggle.

Integrations overview

Browse all available integrations and connection types.

Memory & Learnings

Learn how Corunner builds organizational memory from observations.

Governance

Review policies for access, approval, and data handling.