PostHog is a major BYO-UI addition because one hosted MCP spans product analytics and SQL, feature flags and experiments, dashboards, error tracking and logs, surveys, CDP, data warehouse objects, and support workflows, with built-in session scoping controls.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Organizations and projects; events, persons, actions, cohorts, insights, dashboards, notebooks, and HogQL/SQL; feature flags, experiments, and early-access features; errors, logs, alerts, and annotations; surveys and support conversations; CDP functions and workflows; data warehouse sources, views, endpoints, and pipelines; plus AI-observability and agent-stack objects.
Query analytics and SQL; inspect schemas, events, persons, cohorts, insights, dashboards, replays, flags, experiments, errors, logs, surveys, CDP, warehouse assets, support conversations, and AI-observability data within the authenticated context.
Create, update, launch, pause, archive, resolve, reply, materialize, or delete supported objects across flags, experiments, actions, cohorts, dashboards, alerts, annotations, error tracking, surveys, support tickets, CDP/workflows, warehouse views/endpoints/pipelines, settings, and other cataloged products.
OAuth is recommended and automatically routes the signed-in account to US or EU. Clients without OAuth can use a personal API key created with the project-scoped MCP Server preset; enterprise customers can use IdP-managed authorization. Sessions can also be pinned to an organization or project.
PostHog advises reviewing tool calls for prompt-injection risk. Operators can exclude all writes with `readonly=true`, pin organization/project context, restrict feature categories, or expose exact tool names; BYO-UI should use those server controls before relying on conversational confirmation.
MCP calls share PostHog API limits per team across all users and keys; some AI-powered tools have lower limits, require organization-level AI data processing, and may incur PostHog AI spend. The server has hundreds of tools, so most clients use token-optimized CLI mode; analytics results are returned to the AI client even though the MCP proxy does not store them.
First-party access
Agent access
Support: Official MCP server
Read scope: Product analytics/HogQL and schema discovery; persons, cohorts, dashboards, and replays; flags and experiments; errors and logs; surveys and support; CDP and warehouse assets; AI-observability and agent-stack inspection.
Write scope: Broad operational writes are documented, including feature and experiment lifecycle, dashboard/cohort/action management, error-triage rules and status, support replies, CDP/workflow and warehouse configuration, surveys, alerts, annotations, and project/user settings.
Authentication: Hosted OAuth with automatic US/EU routing; project-scoped personal API key fallback using the MCP Server preset; enterprise IdP-managed authorization option.
Approval boundary: PostHog does not present a universal MCP approval workflow; it tells users to review tool calls. For enforceable boundaries, configure read-only mode, pin the project, and filter to required features or tool names before the session; add BYO-UI confirmation for the remaining destructive or production-impacting calls.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that PostHog ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Hosted endpoint and routing; cross-product reads/writes; catalog scale; OAuth/API-key/IdP auth; pinning, read-only, and tool filtering; rate, AI-spend, and result-flow limits
Full first-party MCP overview, tool-catalog, and operational-control review completed 2026-07-22
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Exact tool names and read/write/lifecycle operations
Exact tool names and read/write/lifecycle operations reviewed from live first-party material on 2026-07-22.
MCP auth, permissions, exposure controls, limits, and privacy behavior
MCP auth, permissions, exposure controls, limits, and privacy behavior reviewed from live first-party material on 2026-07-22.
PostHog documents SQL and HogQL access across PostHog event, person, and connected external-source data. Ad-hoc query access is distinct from recurring bulk exports, which use batch-export capabilities.
Targeted first-party access review
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
