Debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/<id> or /ai-observability/sessions/<id>), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against `events.properties.$ai_input` / `$ai_output_choices` returns empty — message content lives only on the dedicated `posthog.ai_events` table.

🔥🔥🔥✓ VerifiedFreeQuick setup

exploring-autocapture-events

★ 49

by posthog

Guides exploration of $autocapture events captured by posthog-js to understand user interactions, find CSS selectors (especially data-attr attributes), evaluate selector uniqueness, query matching clicks ad-hoc, and create actions. Use when the user asks about autocapture data, wants to find what users are clicking, needs to build actions from click events, asks about elements_chain, wants to build a trend or funnel filtered by clicks or other autocapture interactions, asks which properties autocapture sends, or asks how to filter $autocapture events. Only applies to projects using posthog-js autocapture.

🔥🔥🔥✓ VerifiedFreeAdvanced setup

exploring-llm-costs

★ 49

by posthog

Investigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.

🔥🔥🔥✓ VerifiedFreeQuick setup

exploring-llm-clusters

★ 49

by posthog

Investigate AI observability clusters — understand usage patterns in AI/LLM traffic, compare cluster behavior, compute cost/latency metrics, and drill into individual traces within clusters.

🔥🔥🔥✓ VerifiedFreeQuick setup

diagnosing-missing-recordings

★ 49

by posthog

Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota/billing scenarios.

🔥🔥🔥✓ VerifiedFreeQuick setup

feature-flags-react

★ 49

by posthog

PostHog feature flags for React applications

🔥🔥Free

logs-go

★ 49

by posthog

PostHog logs for Go

🔥🔥Free

integration-ruby

★ 49

by posthog

PostHog integration for any Ruby application using the Ruby SDK

🔥🔥Free

exploring-apm-traces

★ 49

by posthog

Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP. Use when the user asks about service traces, slow HTTP/database spans, error spans, trace IDs, or span attributes — not AI observability traces or product logs. Uses posthog:query-apm-spans, posthog:apm-trace-get, posthog:apm-services-list, posthog:apm-attributes-list, and posthog:apm-attribute-values-list.

🔥🔥🔥✓ VerifiedFreeQuick setup

auditing-experiments-flags

★ 49

by posthog

Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.

🔥🔥🔥✓ VerifiedFreeQuick setup

omnibus-instrument-logs

★ 49

by posthog

Add PostHog log capture to track application logs. Use after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. Also handles initial OTLP exporter setup if not yet configured.

🔥🔥🔥✓ VerifiedFree

omnibus-instrument-integration

★ 49

by posthog

Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework.

🔥🔥🔥🔥✓ VerifiedFree

logs-other

★ 49

by posthog

PostHog logs for Other Languages

🔥🔥Free

omnibus-instrument-error-tracking

★ 49

by posthog

Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.

🔥🔥🔥🔥✓ VerifiedFree