PostHog MCP integration for AI agents.
Connect AI agents to PostHog through 57 structured actions, including get annotation, add dashboard collaborator, cancel query, and copy dashboard tile. Revi…
- ACTION CONTRACTS
- 57
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the PostHog integration exposes
The PostHog Agent App exposes 57 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent get a posthog annotation by id, add a collaborator to a posthog dashboard, and cancel a posthog async query by project id and query id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected PostHog account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real PostHog capabilities.
Showing 12 of 57 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_annotationREADGet a PostHog annotation by ID.
INPUTS: project_id / id
add_dashboard_collaboratorWRITEAdd a collaborator to a PostHog dashboard.
INPUTS: project_id / dashboard_id / user_uuid / level
cancel_queryHIGH IMPACTCancel a PostHog async query by project ID and query ID.
INPUTS: project_id / query_id
copy_dashboard_tileREVIEWCopy an existing PostHog dashboard tile to another dashboard.
INPUTS: project_id / id / fromDashboardId / tileId
add_persons_to_static_cohortWRITEAdd person UUIDs to a static PostHog cohort.
INPUTS: project_id / id / person_ids
bulk_update_event_definition_tagsWRITEBulk add, remove, or set tags on PostHog event definitions.
INPUTS: project_id / ids / action / tags
bulk_update_property_definition_tagsWRITEBulk add, remove, or set tags on PostHog property definitions.
INPUTS: project_id / ids / action / tags
create_annotationWRITECreate an annotation in a PostHog project.
INPUTS: project_id / content / date_marker / creation_type / dashboard_item
create_cohortWRITECreate a cohort in a PostHog project.
INPUTS: project_id / name / description / groups / deleted
create_dashboardWRITECreate a PostHog dashboard in a project.
INPUTS: project_id / name / description / pinned / deleted
create_event_definitionWRITECreate an event definition for a PostHog project.
INPUTS: project_id / name / owner / description / tags
create_feature_flagWRITECreate a feature flag in a PostHog project.
INPUTS: project_id / key / name / filters / active
INPUT CONTRACTS
Know what the action needs before it runs.
get_annotation
project_idOPTIONAL- Project ID of the project to access.
idOPTIONAL- Identifier accepted by the official PostHog API path.
add_dashboard_collaborator
project_idOPTIONAL- Project ID of the project to access.
dashboard_idOPTIONAL- Identifier accepted by the official PostHog API path.
user_uuidOPTIONAL- User UUID to add as a collaborator.
levelOPTIONAL- Restriction level to grant to the collaborator.
cancel_query
project_idOPTIONAL- Project ID of the project to access.
query_idOPTIONAL- Asynchronous query identifier returned by PostHog.
copy_dashboard_tile
project_idOPTIONAL- Project ID of the project to access.
idOPTIONAL- Identifier accepted by the official PostHog API path.
fromDashboardIdOPTIONAL- Dashboard ID the tile currently belongs to.
tileIdOPTIONAL- Dashboard tile ID to copy.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Annotation
Get a PostHog annotation by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_annotationControl Add Dashboard Collaborator
Add a collaborator to a PostHog dashboard. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_dashboard_collaboratorVerify with Add Dashboard Collaborator
Add a collaborator to a PostHog dashboard. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_dashboard_collaboratorSAFETY BOUNDARY
Operate PostHog with explicit limits
- Authorize PostHog with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 28 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `cancel_query`, `delete_annotation`, and `delete_cohort` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in PostHog rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the PostHog task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
PostHog personal API key used with the Authorization Bearer header. Create or manage it at https://us.posthog.com/settings/user-api-keys or https://eu.posthog.com/settings/user-api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 27
- WRITE SIGNALS
- 19
- HIGH IMPACT
- 9
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by PostHog.