Skip to content

PostHog

Updated View as Markdown

Inspect saved insights and feature flag configuration. Review existing analytics context without running fresh queries or evaluating flags.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Review saved insights

List 20 saved PostHog insights from project 42, starting at offset 0. Group them by the question they measure and identify which I should inspect for an activation review. Use saved insight definitions only; do not run fresh queries or create insights.

Explore this command: posthog.insights.list

Check feature flag configuration

Read one page of 20 feature flags in PostHog project 42. Summarize their saved configuration and highlight flags that merit a closer review. Do not evaluate, enable, disable or modify a flag.

Explore this command: posthog.flags.list

What you can do (4)

What you can do

Available commands: 4 (4 read, 0 write). Enable only the commands your application needs.

Command Effect
List one page of saved insights — posthog.insights.list Read
Read one saved insights — posthog.insights.get Read
List one page of feature flags — posthog.flags.list Read
Read one feature flags — posthog.flags.get Read

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for PostHog, then enter the issued values in the connection form below.

  1. In PostHog, open Personal settings > Personal API keys. Create a dedicated personal key limited to the required project with insight:read and feature_flag:read. Public phc_ project tokens cannot authorize these commands.

  2. Choose your US or EU Cloud region in Tooluse.net, enter the personal key and select the reads you need. Self-hosted instances are not supported by this connector.

  3. List commands require an explicit limit of 1–100 and an offset. Insights return saved definitions from the cache. Inspect feature flag configuration without evaluating or changing it. Disconnect here and revoke the personal key in PostHog when finished.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
PostHog Cloud region Required
PostHog personal API key Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "path": {
      "project_id": 42
    },
    "query": {
      "limit": 20,
      "offset": 0
    }
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

List one page of saved insights — posthog.insights.list

Reads saved metadata only. Insight refresh is pinned to force_cache; no analytics query is launched.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.project_id integer Required minimum: 1; maximum: 9007199254740991
query object Required additionalProperties: false
query.limit integer Required minimum: 1; maximum: 100
query.offset integer Required minimum: 0; maximum: 100000

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "project_id": 42
  },
  "query": {
    "limit": 20,
    "offset": 0
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

Read one saved insights — posthog.insights.get

Reads saved metadata only. Insight refresh is pinned to force_cache; no analytics query is launched.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.project_id integer Required minimum: 1; maximum: 9007199254740991
path.id integer Required minimum: 1; maximum: 9007199254740991

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "project_id": 42,
    "id": 7
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

List one page of feature flags — posthog.flags.list

Reads saved metadata only. Insight refresh is pinned to force_cache; no analytics query is launched.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.project_id integer Required minimum: 1; maximum: 9007199254740991
query object Required additionalProperties: false
query.limit integer Required minimum: 1; maximum: 100
query.offset integer Required minimum: 0; maximum: 100000

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "project_id": 42
  },
  "query": {
    "limit": 20,
    "offset": 0
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

Read one feature flags — posthog.flags.get

Reads saved metadata only. Insight refresh is pinned to force_cache; no analytics query is launched.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.project_id integer Required minimum: 1; maximum: 9007199254740991
path.id integer Required minimum: 1; maximum: 9007199254740991

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "project_id": 42,
    "id": 7
  }
}

At most 1 provider requests per invocation; timeout: 20 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close