Product Ops (Stripe, Sentry, PostHog)

Run the operational side of a product from a coding agent: errors in Sentry, product analytics and feature flags in PostHog, payments in Stripe, and one health check that reads all three together.

Start with /product-health-check for a combined picture of the last day or week, or ask directly: "debug this Sentry issue", "why did sign-ups drop", "add analytics events to this feature", "set up an alert".

You sign in to each service on first use. The three MCP servers are the vendors' hosted ones and use OAuth: Sentry (https://mcp.sentry.dev/mcp), PostHog (https://mcp.posthog.com/mcp) and Stripe (https://mcp.stripe.com). Nothing works for a service until you have signed in to it; the services you do not use can stay signed out. PostHog bills its AI-powered tools as PostHog AI usage.

Third-party skills, imported unmodified: sentry-get-started, sentry-instrument, sentry-debug-issue, sentry-create-alert from https://github.com/getsentry/sentry-for-ai (MIT); instrument-product-analytics, instrument-feature-flags, querying-posthog-data, building-a-dashboard, investigate-metric from https://github.com/PostHog/skills (MIT, marked by PostHog as under construction). Stripe is used through its MCP server only. Not affiliated with Stripe, Sentry or PostHog.

These servers can change live data. The setup's rules make the agent read by default and ask before every write; prefer Stripe test mode and restricted access while you try it.