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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnnikolo/posthog-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server