:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Sharing feedback on PostHog
The agent-feedback tool is a direct channel to the PostHog team for feedback about anything PostHog — a product or feature you (or the user) hit a rough edge with, this MCP server itself, the docs, or a capability that's missing. Use it whenever you or the user run into something worth telling the PostHog team, on any surface.
Set feedback_type to route it:
product— any PostHog product or feature: insights, session replay, feature flags, the data warehouse, web analytics, error tracking, experiments, etc. Put the area inproduct_area(e.g. "session replay").mcp— this MCP server itself: an unclear tool description, a confusing input schema, a hard-to-consume response, wrong results, an unhelpful error, a missing tool, or these instructions. Setcategoryfor MCP feedback.docs— PostHog documentation.scout— reserved for scheduled scout runs: an improvement opportunity in the canonical PostHog-authored scout skill steering the run (a false positive its rules produced, a detection its instructions missed, a discriminator that doesn't hold on this class of project). Setscout_skill_name,scout_skill_version, andscout_category, and generalize the observation — describe the pattern, never this project's data.other— anything that doesn't fit the above.
All sentiments are welcome — set sentiment to positive, neutral, negative, or mixed. Unlike a bug tracker, praise and feature requests are useful signal too, not just problems. Good triggers: a confusing or broken product experience, a papercut that slowed the task down, a missing capability you had to work around, a feature request, an unhelpful error, or something that worked really well and is worth reinforcing.
Keep it short and actionable: a one-sentence summary, then the detail fields (friction_points, suggested_improvement, details) as clear, concise bullet points, quoting the exact product surface, tool name, parameter, or error text where you can. Include a concrete suggested_improvement whenever you can name one — for negative or mixed feedback that's the most valuable part. Use task_completed: false when you couldn't finish the user's request. Do not include user PII or sensitive query content in any field.
The user can also ask you to send feedback directly — e.g. "make a PostHog feedback for this, it's broken." When they do, capture their point faithfully and submit it.
Submitting feedback is not a way to end your turn or skip work. It's a side report to the PostHog team — call it when warranted, then keep going and finish the user's task with the other tools.