- Home
- Resources
- Integrations
- PostHog
Claude PostHog connectorWhat Claude can do in your PostHog account.
The Claude PostHog connector exposes 57 tools. 19 read insights, flags, experiments, surveys and projects, 19 create, update or delete them, and 19 carry names no source describes. Below: what Claude reads, what it can ship or remove, and what to review.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can work in your PostHog
PostHog bundles product analytics, feature flags, experiments and surveys. With the connector, you stop hunting through tabs: you ask Claude how an experiment is doing or which flags are live, it reads your PostHog project, and it can also create or edit those objects when you ask. PostHog itself says the agent can read and write across its products.
Read an experiment's verdict. A product manager wants to know whether the new onboarding test is winning. Claude opens it with experiment-get and reads metric and exposure results through experiment-results-get.
Ship or clean up a feature flag. create-feature-flag, update-feature-flag and delete-feature-flag let Claude handle flags from the conversation, after feature-flag-get-all shows what exists.
Follow a survey. survey-stats gives the response statistics of one survey and surveys-global-stats the totals across all of them, so Claude can summarize feedback without an export.
What to keep in mind: 19 names on the sheet, including queries, error tracking and logs, match nothing in PostHog's tool reference, so no source describes them. Deleting tools exist for insights, dashboards, flags, experiments, surveys and actions. Nothing runs on its own either: a flag does not roll out because a metric moved, and no survey launches by itself. For events pushed into PostHog from other apps, the PostHog n8n integration covers workflows that run unattended. Different jobs; the Integrations hub lists the rest.
Five words before you connect
The vocabulary of this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector gives Claude. Claude chooses the tools it needs by itself, and the directory lists them by name.
- Authorization
- PostHog's sign-in step, where you hand Claude access to your account. Granted once, per person, and it can be withdrawn later.
- Approval
- The confirmation Claude waits for before it goes ahead with something that alters your account, shown right in the conversation.
- MCP
- The shared standard behind connectors. It is what lets an assistant like Claude talk to an outside service such as PostHog.
Connect PostHog to Claude in three steps
- 01
Find PostHog in Claude
Open Claude's settings, go to Customize, then Connectors, and look up PostHog. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first, then members sign in individually.
- 02
Start the connection
Click Connect on the PostHog row and log in on the page PostHog opens itself. PostHog says its sign-in routes you to the right data region, US or EU, from your account. If the link breaks, Disconnect and reconnect.
- 03
Read the authorization screen
Check the screen before you accept. It belongs to PostHog, not to Claude, and it sets what the access covers. It may list broader rights than Claude uses day to day; asking before each action remains the default.
The 57 tools of the Claude PostHog connector
PostHog gives Claude 57 tools: 19 that read your account, 19 that change something in it, and 19 no official source describes.
Three groups: what Claude reads, what it changes, and names no official text describes. Tool names stay exactly as Claude shows them.
- 19 read
- 19 write
- 19 not documented
Tools index
- insight-get
- insight-query
- dashboard-get
- dashboards-get-all
- feature-flag-get-definition
- feature-flag-get-all
- experiment-get
- experiment-results-get
- survey-get
- surveys-get-all
- survey-stats
- surveys-global-stats
- action-get
- actions-get-all
- get-llm-total-costs-for-project
- read-data-schema
- organizations-get
- projects-get
- docs-search
- insight-update
- insight-delete
- dashboard-create
- dashboard-update
- dashboard-delete
- dashboard-reorder-tiles
- create-feature-flag
- update-feature-flag
- delete-feature-flag
- experiment-create
- experiment-update
- experiment-delete
- survey-create
- survey-update
- survey-delete
- action-create
- action-update
- action-delete
- event-definition-update
- query-run
- query-generate-hogql-from-question
- insight-create-from-query
- insights-get-all
- add-insight-to-dashboard
- experiment-get-all
- list-errors
- error-details
- logs-query
- logs-list-attributes
- logs-list-attribute-values
- event-definitions-list
- properties-list
- execute-sql
- read-data-warehouse-schema
- organization-details-get
- switch-organization
- switch-project
- entity-search
What Claude reads (19)
19 toolsNineteen tools that look at insights, dashboards, flags, experiments, surveys, actions, costs and projects, and leave them untouched.
insight-get
Opens one saved insight, PostHog's name for a saved analysis or chart, so Claude can tell you what it measures and how it is set up.
insight-query
Runs the query behind a saved insight and returns the results, so the numbers are fresh rather than whatever was cached.
dashboard-get
Returns one dashboard, so Claude can describe which insights it holds and what the board is meant to follow.
dashboards-get-all
Lists every dashboard in the project, giving Claude the full map before it opens any single one.
feature-flag-get-definition
Reads the definition of one feature flag, meaning how it is set up, so Claude can explain who gets the feature and on what conditions.
feature-flag-get-all
Lists all feature flags in the project, the starting point for any cleanup or audit of what is live.
experiment-get
Returns the details of one experiment, its setup and configuration, so Claude can tell you what is being tested and how it is measured.
experiment-results-get
Fetches an experiment's metric and exposure results, with metadata describing each metric, so Claude can read the outcome with you.
survey-get
Opens one survey by its ID to show its questions and settings, which Claude can then walk you through.
surveys-get-all
Lists the surveys in the project, with server-side search and filters, so Claude can find the one you mean from just a few words.
survey-stats
Returns the response statistics of one specific survey, which Claude can then summarize in plain words for you.
surveys-global-stats
Returns aggregated response statistics across every survey in the project, a bird's-eye view of how much feedback comes in.
action-get
Opens one action, PostHog's way of grouping events under a single name, to show exactly how it is defined.
actions-get-all
Lists all the actions defined in the project, so Claude knows which named behaviors already exist before building anything on top of them.
get-llm-total-costs-for-project
Fetches the total daily LLM costs of a project for each model over a number of days you choose.
read-data-schema
Explores your events, actions, properties and property values, so Claude learns how your data is structured before answering questions about it.
organizations-get
Fetches the PostHog organizations you have access to, which tells Claude where it is allowed to look.
projects-get
Fetches the projects you can reach in the current organization, so Claude picks the right one before running any query.
docs-search
Searches PostHog's documentation, so Claude can back an answer with the vendor's own explanation instead of relying on memory.
What Claude changes (19)
19 toolsNineteen tools that create, alter or remove PostHog objects. No source gives them a confirmation of their own, so the general rule below applies.
insight-update
Approval: see the ruleChanges a saved insight, for instance its name, description or settings.
insight-delete
Approval: see the ruleRemoves a saved insight from the project.
dashboard-create
Approval: see the ruleSets up a new dashboard in the project, ready to hold insights.
dashboard-update
Approval: see the ruleModifies an existing dashboard, such as its name, description or settings.
dashboard-delete
Approval: see the ruleDeletes a dashboard from the project.
dashboard-reorder-tiles
Approval: see the ruleRearranges the tiles of a dashboard, the order in which its insights appear.
create-feature-flag
Approval: see the ruleCreates a new feature flag in the project, ready to gate a feature.
update-feature-flag
Approval: see the ruleUpdates an existing feature flag, which alters who sees the feature it controls.
delete-feature-flag
Approval: see the ruleDeletes a feature flag.
experiment-create
Approval: see the ruleAdds a new experiment to the project in PostHog, ready to be configured and launched.
experiment-update
Approval: see the ruleAlters an existing experiment's settings.
experiment-delete
Approval: see the ruleDeletes an experiment from the project, setup included.
survey-create
Approval: see the ruleBuilds a new survey in the project, which PostHog can then show to users.
survey-update
Approval: see the ruleRewrites an existing survey, found by its ID, such as its questions or settings.
survey-delete
Approval: see the ruleDeletes a survey by its ID.
action-create
Approval: see the ruleCreates an action, grouping events under one name you can then analyze.
action-update
Approval: see the ruleRedefines an existing action, which alters every insight built on it.
action-delete
Approval: see the ruleDeletes an action from the project, along with the grouping it defined.
event-definition-update
Approval: see the ruleUpdates an event definition's metadata, the descriptive layer around an event rather than the event data itself.
Undocumented (19)
19 toolsThese nineteen names sit on the directory sheet with no matching entry in PostHog's tool reference, or with a line that does not say whether they read or alter anything.
query-run
This name appears on the directory sheet but nowhere in PostHog's tool reference, and no Claude page describes it. The page therefore says nothing about what it does or what it returns.
query-generate-hogql-from-question
Listed by the directory, absent from PostHog's reference under this exact name. No source describes it, so its behavior stays unknown on this page, however clear the name may look.
insight-create-from-query
No tool spelled this way appears in PostHog's current reference. Without a sentence naming it, the page cannot say whether it only reads or also alters your project, and does not try.
insights-get-all
The reference documents single-insight tools, not this plural name. No official text describes this one, so the page leaves it unexplained rather than borrow the description of a neighboring tool with a similar name.
add-insight-to-dashboard
Nothing in PostHog's reference or Claude's help pages matches this name. The directory publishes it without a description, and so does this page, on purpose, until a source says more.
experiment-get-all
The reference covers other experiment tools but not this one under this name. No source describes it, and the page does not stretch a name into a capability it cannot source from any official page.
list-errors
PostHog's overview gives an example of asking for top errors, but no source ties that to this exact tool name. It stays undocumented on this page.
error-details
No official page documents a tool with this name. Whatever it returns is not stated by any source, so nothing is claimed about it here, not even whether it only reads.
logs-query
PostHog mentions logs among its products, yet its reference has no entry for this name. No description exists to reformulate, so the page stops at the name and reports the gap.
logs-list-attributes
Another log-related name with no matching line in the tool reference and no Claude page behind it. Its effect is not documented anywhere public, and the page leaves it that way.
logs-list-attribute-values
Same situation as its neighbor: the directory lists it, no official source describes it. The page does not guess from the wording, even when the wording looks obvious at first glance.
event-definitions-list
PostHog's reference has an entry on event definitions under another name, but none under this one. With no sentence about it, nothing sourced can be said about its effect on your project.
properties-list
No entry in PostHog's reference carries this name, and no Claude page mentions it. Its role is therefore not documented here, and no neighboring description stands in for it on this page.
execute-sql
PostHog's reference says only that it executes an SQL query. No source says whether that query is limited to reading, so the page cannot place it on either side.
read-data-warehouse-schema
A sibling of a documented schema tool, but this exact name has no line in PostHog's reference. Nothing official describes it, so the documented sibling's behavior is not assumed for it.
organization-details-get
The only organization tool in PostHog's reference lists organizations, and it is not this one. No official sentence covers this name, so the page leaves it without a description.
switch-organization
According to the tool reference, it sets which organization is active for the tool calls that follow. No source says whether that counts as reading or altering anything, so it stays in this group.
switch-project
According to PostHog, it sets the active project for later tool calls. Whether that touches your data at all is not stated by any source, which is why the page does not classify it.
entity-search
Search as it may sound, this name has no entry in PostHog's reference, and no Claude page describes it. The page reports the gap instead of filling it with a guess.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. The prompt appears in the conversation when it matters.
No source gives any PostHog tool its own confirmation, so this default covers the whole list, deletions included. PostHog adds a warning of its own: models can be tricked into following untrusted instructions, so review each tool call before it runs. On Team and Enterprise workspaces, owners decide whether a member may skip the prompt for some actions and can restrict a connector for the whole organization. Claude also works with the rights of the person who connected and nothing wider.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer for one connector is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members connect. For this connector's live state, check the PostHog sheet in the official directory. On PostHog's side, connecting and calling tools costs nothing, though some tools run AI internally and may count as PostHog AI spend.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so no flag rolls out and no survey launches because a metric crossed a line.
Everything here comes from PostHog's documentation and the directory sheet: no Claude help article covers this connector. The tool list is an observed floor, and PostHog's reference lists far more tools than the sheet under partly different names. The partner badge is not a security audit, and Anthropic says on every sheet that it neither picks a publisher's tools nor guarantees their behavior. Connect it knowing it comes from PostHog.
Need help connecting PostHog to Claude?
A person reads every message.