Skip to main content
Query analytics, feature flags, and errors. The PostHog MCP connector gives agents direct access to your PostHog data — querying insights, managing feature flags, tracking errors, and browsing dashboards.
This page covers the PostHog MCP connector for agent tool access. For PostHog as an automation trigger (via webhooks), see PostHog.

Setup

  1. Go to Integrations and find PostHog
  2. Click Connect
  3. Enter your PostHog personal API key (get one here — use the “MCP Server” preset for recommended scopes)
  4. Click Save — Proliferate will test the connection automatically

Available tools

ToolDescription
feature-flag-get-definitionGet a feature flag’s definition and rollout settings
feature-flag-get-allList all feature flags
create-feature-flagCreate a new feature flag
update-feature-flagUpdate a feature flag’s configuration
delete-feature-flagDelete a feature flag
insights-get-allList all insights
insight-getGet a specific insight
insight-create-from-queryCreate an insight from a query
insight-updateUpdate an insight
insight-deleteDelete an insight
dashboards-get-allList all dashboards
dashboard-getGet a specific dashboard
dashboard-createCreate a new dashboard
dashboard-updateUpdate a dashboard
dashboard-deleteDelete a dashboard
add-insight-to-dashboardAdd an insight to a dashboard
list-errorsList errors with filtering and sorting
error-detailsGet detailed error information
get-sql-insightRun HogQL queries
property-definitionsGet property definitions
get-llm-total-costs-for-projectGet LLM cost tracking data
organizations-getList organizations
organization-set-activeSet the active organization
projects-getList projects
project-set-activeSet the active project
docs-searchSearch PostHog documentation

Use cases

  • Toggle feature flags as part of deployment automations
  • Query error details when an automation is investigating an incident
  • Pull analytics insights (conversion funnels, user trends) to inform automated reporting
The tools listed above may not be exhaustive and can change as PostHog updates their MCP server. See PostHog API documentation for the latest.