posthog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTHOG_HOST | No | Override for self-hosted PostHog instances | https://app.posthog.com |
| POSTHOG_API_KEY | Yes | Your PostHog personal API key | |
| POSTHOG_PROJECT_ID | Yes | The numeric project ID to query |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_insightsA | Fetch a PostHog insight by ID and return its result data. Use this to retrieve saved insights like funnels, retention, or trend charts. |
| list_eventsA | Fetch recent events from a PostHog project. Supports filtering by event name and date range. Returns up to 100 events by default. |
| get_feature_flagsB | List all feature flags in the project with their keys, enabled status, rollout percentages, and targeting conditions. |
| query_trendsB | Run a trends query to get event counts over time. Returns a time series of event occurrences, optionally broken down by a property. |
| get_personsB | Look up person profiles in PostHog. Can search by distinct ID or return a paginated list of persons with their properties. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct PostHog resource: feature flags, insights, persons, events, and trends. There is no overlap in functionality, making it clear which tool to use for each task.
The naming pattern is inconsistent: three tools use 'get_', one uses 'list_', and one uses 'query_'. Furthermore, 'get_insights' suggests a single insight but actually retrieves by ID, while 'get_feature_flags' returns a list. This could cause confusion.
With five tools, the server covers essential read operations for a PostHog integration. The count is reasonable but slightly on the low side for a comprehensive analytics platform; it could include a few more tools.
The tool surface is entirely read-only, missing create, update, and delete operations for all resources. There are no tools for managing cohorts, experiments, or dashboards, leaving significant gaps for typical PostHog workflows.