
Posthog Mcp Server
Let your agent query PostHog events, persons, insights, and dashboards to debug funnels and product usage while you ship iterations.
Overview
io.github.friendlygeorge/posthog-mcp-server is a MCP server for the Grow phase that lets AI assistants query PostHog product analytics including events, persons, insights, and dashboards.
What is this MCP server?
- Query PostHog events, persons, and user properties from the agent
- Fetch insights, dashboards, and product analytics context for AI assistants
- stdio npm posthog-mcp-server v1.0.0
- Supports debugging funnels and feature adoption without SQL exports
- Pairs with PostHog project API keys in MCP config
- MCP server version 1.0.0
- Transport: stdio
- npm identifier: posthog-mcp-server
What problem does it solve?
Product questions stall when you must leave the agent, open PostHog, and manually reconstruct events and insights.
Who is it for?
Solo SaaS founders already on PostHog who want agents to investigate behavior, insights, and dashboards during growth work.
Skip if: Greenfield projects with no PostHog instrumentation, or teams that only use Plausible for marketing-site stats.
What do I get? / Deliverables
You get in-chat access to PostHog analytics data so funnel checks and usage summaries inform the next build or growth move.
- PostHog-connected MCP server in agent config
- Agent tools for events, persons, and insights queries
- Faster product analytics answers during growth sessions
Recommended MCP Servers
Journey fit
How it compares
PostHog query MCP integration, not an instrumentation or feature-flag authoring skill.
Common Questions / FAQ
Who is posthog-mcp-server for?
Builders running PostHog on their product who want Claude Code or Cursor to pull events, persons, and insights for debugging and planning.
When should I use posthog-mcp-server?
Use it in Grow when analyzing activation, retention experiments, or dashboard metrics before prioritizing fixes or content.
How do I add posthog-mcp-server to my agent?
Install posthog-mcp-server from npm, configure stdio MCP with your PostHog host and personal API key, then reload the agent.