Posthog
Wire PostHog event capture, feature-flag checks, and project management into your coding agent while you ship and iterate solo.
Overview
com.mcparmory/posthog is a MCP server for the Grow phase that lets your agent capture analytics events, evaluate feature flags, and manage PostHog projects over stdio.
What is this MCP server?
- Capture product analytics events from agent-driven workflows without leaving the IDE
- Evaluate feature flags to gate experiments and rollouts while coding
- Manage PostHog projects and related configuration through MCP tools
- Ship via stdio with uvx (PyPI mcparmory-posthog 1.0.5) or Docker ghcr.io/mcparmory/posthog:1.0.5
- Server version 1.0.5 per MCP registry schema
- 2 distribution packages: PyPI (uvx) and OCI Docker image
- Transport type stdio for both packages
Community signal: 25 GitHub stars.
What problem does it solve?
You are shipping features fast but toggling flags and defining events means context-switching out of your agent into PostHog every time.
Who is it for?
Indie SaaS builders who already use PostHog and want the agent to instrument events and flags while implementing growth experiments.
Skip if: Teams that need a full analytics strategy or warehouse pipeline without a PostHog account and API access.
What do I get? / Deliverables
Your agent can record events and check flags in conversation so instrumentation keeps pace with code changes.
- Agent-callable PostHog tools for events, flags, and projects
- stdio MCP configuration entry for your agent
- Repeatable instrumentation workflow tied to your codebase
Recommended MCP Servers
Journey fit
Product analytics and experimentation belong after you have something to measure and optimize, not during raw ideation. Analytics subphase is where builders instrument funnels, cohorts, and flags to see whether launches and changes actually move retention or revenue.
How it compares
MCP bridge to PostHog APIs, not a standalone analytics skill or BI dashboard.
Common Questions / FAQ
Who is com.mcparmory/posthog for?
Solo and small-team builders using PostHog who want their AI coding agent to handle events, flags, and project tasks via MCP.
When should I use com.mcparmory/posthog?
Use it in Grow when you are adding tracking, running feature-flagged rollouts, or adjusting PostHog project setup alongside product changes.
How do I add com.mcparmory/posthog to my agent?
Register the server in your MCP client with stdio, using uvx for mcparmory-posthog 1.0.5 or the ghcr.io/mcparmory/posthog:1.0.5 Docker image, and supply your PostHog API credentials.