: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.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
URL patterns
PostHog app links must be full URLs (origin + path) — bare paths aren't clickable in MCP clients like Cursor or Claude Desktop. Use Markdown with descriptive anchor text, e.g. [Cohorts](https://us.posthog.com/project/1/cohorts). Never include /-/.
Choose the link source in this order:
- If a tool result has a
*urlfield (e.g._posthogUrl), surface it verbatim — never rewrite or strip it. - Only when you actually want to link a specific entity (or the user asks for a link) and it has no
_posthogUrl, callgenerate-app-urland surface theurlverbatim — don't hand-write slugs or retype IDs into paths, both are easy to get wrong. Don't fetch a link just because a result has an ID. - Only for genuinely static pages not in the
generate-app-urlcatalog (some settings pages), take the origin from a PostHog URL you already have (any_posthogUrl, or agenerate-app-urlresult). Then build the link (don't double-prefix):- Project-scoped paths → origin +
/project/<active project id>, never an id copied from another URL:/settings/<section-id>(hyphenated, e.g./settings/environment-replay,/settings/user-api-keys). - Org-/account-level paths → origin only (no
/project/:id): first segmentorganization,me,account, orinstance— e.g. billing is/organization/billing.
- Project-scoped paths → origin +