"PostHog" matching MCP servers:

Enables AI agents to query PostHog analytics data directly via tool calls, including insights, events, feature flags, trends, and persons.

Enables querying PostHog analytics data by fetching recent events, searching user profiles, and listing saved insights over MCP.

Enables interaction with PostHog's product analytics platform through natural language, allowing users to manage feature flags, view errors, and access other platform features.

Enables querying PostHog with HogQL, retrieving event and property definitions, session replays, and project lists, plus optional REST API access with safeguards against accidental writes and API key leakage.

Enables interaction with a self-hosted PostHog instance through MCP, providing access to PostHog analytics and product data.

A minimal MCP server built with NestJS to test PostHog MCP analytics integration, exposing mocked tools for trends and funnel analysis.

It enables solo builders to automatically log product changes to PostHog and later get statistically honest verdicts on whether those changes moved key metrics, without needing enough traffic for A/B tests.

A server that implements the Model Context Protocol (MCP) on Cloudflare Workers, allowing AI models to access custom tools without authentication.

Enables read-only inspection of Depot CI failures, job logs, GitHub Actions jobs on Depot runners, and container builds through the Depot API, so agents can diagnose issues without installing the Depot CLI.

Enables incident responders to query and correlate observability and DevOps evidence across Grafana, Prometheus, Loki, Uptime Kuma, CloudWatch, IAM, and PostHog from a local MCP client, with bounded reads and redacted audit records.