Ext Ops Panel
Open dashboard

What it can do: posthog

Plugin bundle · PostHog

What posthog declares, asks for and runs, according to the marketplaces we read. Runs on a remote server: your AI tool connects to it over the network. mcp.posthog.com/mcp. None of the marketplaces we read publishes its tools or the settings it asks for. As of our marketplace pass on 2026-10-12.

This is not a security audit. We list what the marketplaces publish about this plugin: what it declares, what it asks for and what it runs. We do not run or inspect its code, and a verified mark is the marketplace's statement, not ours.

Where it runs

  • Runs on a remote server: your AI tool connects to it over the network. mcp.posthog.com/mcpTransport: Streamable HTTP. As declared on: Claude Code: claude-plugins-official, Claude Code: claude-plugins-community.

What it declares

None of the marketplaces we read publishes a list of tools for it.

Prompts and resources: the marketplaces we read do not publish them.

What it asks for

None of the marketplaces we read lists environment variables for it.

Names only: we keep no values, examples or descriptions of these variables. OAuth scopes and install-time settings are not published by the marketplaces we read.

What it runs besides MCP

Skills: 161 As declared on: Claude Code: claude-plugins-official.

  • adding-warehouse-person-properties
  • analyzing-expensive-users
  • analyzing-experiment-session-replays
  • analyzing-task-runs
  • assessing-heatmaps
  • auditing-endpoints
  • auditing-experiments-flags
  • auditing-warehouse-source-health
  • auditing-warehouse-view-health
  • authoring-data-quality-checks
  • authoring-error-tracking-alerts
  • authoring-log-alerts
Show the remaining 149
  • authoring-scouts
  • building-a-dashboard
  • building-canvases
  • building-html-canvases
  • building-loops
  • building-react-quill-canvases
  • building-workflows
  • checking-deploy-timing
  • checking-member-access
  • choosing-trend-or-slope-view
  • cleaning-up-stale-feature-flags
  • composing-grid-canvases
  • configuring-experiment-analytics
  • configuring-experiment-rollout
  • consuming-endpoints-from-client-code
  • context-layer-consolidation
  • context-layer-dreaming
  • context-layer-health-check
  • copying-endpoints-across-projects
  • copying-flags-across-projects
  • creating-ai-subscription
  • creating-an-endpoint
  • creating-box-plot-insights
  • creating-experiments
  • creating-online-evaluations
  • creating-replay-vision-scanners
  • creating-surveys
  • debugging-experiments
  • debugging-surveys
  • designing-email-templates
  • diagnosing-ci-and-merge-bottlenecks
  • diagnosing-endpoint-performance
  • diagnosing-experiment-results
  • diagnosing-failed-warehouse-syncs
  • diagnosing-missing-recordings
  • diagnosing-sdk-health
  • diagnosing-stacktrace-symbolication
  • downloading-batch-export-files
  • exploring-ai-failures
  • exploring-apm-traces
  • exploring-autocapture-events
  • exploring-endpoint-execution-logs
  • exploring-live-traffic
  • exploring-llm-clusters
  • exploring-llm-costs
  • exploring-llm-evaluations
  • exploring-llm-traces
  • exploring-mcp-intent-clusters
  • exploring-mcp-sessions
  • exploring-mcp-tool-original-user-motive
  • exploring-mcp-tool-quality
  • exploring-mcp-tool-usage
  • exploring-replay-vision-observations
  • exploring-scouts
  • feature-usage-feed
  • filtering-bot-traffic
  • finding-deleted-feature-flags
  • finding-experiments
  • finding-replay-for-issue
  • finding-sessions-to-watch
  • formatting-insight-axes
  • grouping-noisy-errors
  • inbox-exploration
  • instrument-error-tracking
  • instrument-feature-flags
  • instrument-integration
  • instrument-llm-analytics
  • instrument-logs
  • instrument-metrics
  • instrument-product-analytics
  • investigate-metric
  • investigating-ci-failures
  • investigating-error-issue
  • investigating-logs
  • investigating-metric-anomalies
  • investigating-replay
  • managing-endpoint-versions
  • managing-experiment-lifecycle
  • managing-path-cleaning-rules
  • managing-reminders
  • managing-streamlit-apps
  • managing-subscriptions
  • modeling-activation-metrics
  • modeling-conversion-metrics
  • modeling-dimension-tables
  • modeling-product-usage-metrics
  • modeling-revenue-metrics
  • modeling-warehouse-foundations
  • querying-canvas-data
  • querying-posthog-data
  • resolving-ingestion-warnings
  • review-hog-authoring
  • review-hog-blind-spots-general
  • review-hog-perspective-contracts-security
  • review-hog-perspective-logic-correctness
  • review-hog-perspective-performance-reliability
  • review-hog-resolution-criteria
  • review-hog-validation-criteria
  • scanning-experiments-with-replay-vision
  • setting-up-a-custom-rest-source
  • setting-up-a-data-warehouse-source
  • setting-up-data-catalog
  • setting-up-warehouse-properties
  • signals
  • signals-scout-ai-observability
  • signals-scout-anomaly-detection
  • signals-scout-apm
  • signals-scout-conversations
  • signals-scout-csp-violations
  • signals-scout-customer-analytics
  • signals-scout-customer-analytics-billing-and-usage
  • signals-scout-data-pipelines
  • signals-scout-data-warehouse
  • signals-scout-error-tracking
  • signals-scout-experiments
  • signals-scout-feature-flags
  • signals-scout-general
  • signals-scout-health-checks
  • signals-scout-inbox-validation
  • signals-scout-insight-alerts
  • signals-scout-logs
  • signals-scout-mcp-tool-calls
  • signals-scout-observability-gaps
  • signals-scout-pr-follow-up
  • signals-scout-product-analytics
  • signals-scout-replay-vision
  • signals-scout-revenue-analytics
  • signals-scout-session-replay
  • signals-scout-skills-store
  • signals-scout-surveys
  • signals-scout-tasks
  • signals-scout-web-analytics
  • signals-scout-web-vitals
  • signals-scout-workflows
  • skills-store
  • suggesting-data-imports
  • suggesting-path-cleaning-rules
  • suppressing-noisy-errors
  • triaging-error-issues
  • triaging-visual-review-runs
  • tuning-incremental-sync-config
  • turning-engineering-analytics-into-insights
  • understanding-billing-usage
  • validating-and-publishing-canvases
  • working-with-scouts
  • working-with-skills
  • working-with-task-comments
  • writing-simplified-technical-english
  • writing-streamlit-apps

Commands: 3 As declared on: Claude Code: claude-plugins-official.

  • llma-cc-ingest
  • llma-cc-setup
  • llma-cc-status

Agents: 1 As declared on: Claude Code: claude-plugins-official.

  • error-analyzer

Hooks: 2 As declared on: Claude Code: claude-plugins-official.

  • PreToolUse
  • SessionEnd

Who answers for it

PostHog

  • No marketplace we read marks it or its publisher as verified.
  • License: MIT.
  • The repository github.com/posthog/ai-plugin belongs to the account the publisher is listed under on Claude Code: claude-plugins-official.

How it has changed

Its tools, settings, hooks and composition have not changed since we started watching it.

In context

  • Median number of secrets a plugin bundle asks for on the marketplaces we read: 0.0. This one asks for: 0.
  • Share of plugin bundles that run on a remote server: 17%.

Where it is published and how its figures have moved

Compare it side by side with similar plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built