01 · Records and state owned
Analytics/HogQL, feature flags, experiments, errors, logs, surveys, CDP destinations and support workflows
PostHog
PostHog
Curated major addition platform in product analytics and experimentation with material relevance to the Marcom operating stack and a first-party developer surface.
Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaSReverse ETL / activation
Concrete capability record
Data, retrieval, actions, identity, and operating limits
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.
02 · Data you can retrieve
Analytics/HogQL, feature flags, experiments, errors, logs, surveys, CDP destinations and support workflows
03 · Actions and write paths
The targeted review confirmed this PostHog capability surface: Analytics/HogQL, feature flags, experiments, errors, logs, surveys, CDP destinations and support workflows. It did not normalize every mutation tool. Treat writes as unapproved until each current tool, scope, plan and approval behavior is verified.
04 · Authentication and permissions
Authentication model is documented by the vendor; inspect the cited source before implementation. Official docs confirm hosted tenant-data MCP with both query and operational tools.
05 · Monitoring, approval, and recovery
Official docs confirm hosted tenant-data MCP with both query and operational tools. Official docs confirm hosted tenant-data MCP with both query and operational tools.
06 · Gaps and implementation limits
Official docs confirm hosted tenant-data MCP with both query and operational tools.
First-party access
Documented surfaces
SQL / HogQL query access ↗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.Source: PostHog SQL editorReverse ETL / export ↗PostHog explicitly lists Reverse ETL and export destinations alongside its data warehouse. Realtime destinations, batch exports, and classic warehouse-to-SaaS Reverse ETL have different execution and governance boundaries.Source: PostHogMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer access
Agent access
MCP and adjacent posture
Verified first-party provider MCPPostHog-hosted remote MCPCurrent hosted endpoint
Role: provider
Read scope: Analytics/HogQL, feature flags, experiments, errors, logs, surveys, CDP destinations and support workflows
Write scope: Write scope was not separately normalized in this pass; inspect the official tool catalog before enabling actions.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Official docs confirm hosted tenant-data MCP with both query and operational tools.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that PostHog ships these experiences.
Single-platform patterns
- Product analytics, replay, and flag-management cockpit
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- PostHog + warehouse or semantic layer: executive insight brief
- PostHog + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“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.
4 recorded sources
MCPRepresentative source
https://posthog.com/docs/model-context-protocol ↗Official docs confirm hosted tenant-data MCP with both query and operational tools.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://posthog.com/docs/api ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://posthog.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
SQL / HogQL query accessTargeted review
PostHog SQL editor ↗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.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.