How to add PostHog MCP
Connect PostHog through Durin and verify an allowed read and a denied request before rollout.
Prepare provider access
Use the named PostHog card with https://mcp.posthog.com/mcp?mode=tools. Keep mode=tools for the individual-tool catalog. Complete provider OAuth and project access; use registered client details when required by your deployment.
Save, review and enable
Open Admin → Connections → All providers. Save an OAuth draft, sign in, discover tools, save permission review and obtain the matching deployed validator. Run an approved read test, review billing, confirm activation and enable the reviewed tool.
Complete personal provider access, copy your Durin connection URL and authenticate your MCP client for that exact URL. Keep credentials and endpoint secrets out of shared evidence.
Read a scoped analytics result
Run one reviewed read query against a test project. Enter arguments from its discovered schema. Configure Durin to deny writes, then attempt the reviewed create-dashboard operation against that same test project.
- Expected success: a result from the authorized test project; activity records allow and a successful execution outcome.
- Expected denial: request dashboard creation under deny-writes policy; the tool may also be absent from discovery; no new provider dispatch. Restore the baseline after testing.
Troubleshooting
Sign-in succeeds but the tool is unavailable
Check personal consent, team access, permitted resources, deployed validator and activation. Discovery and an approved request alone do not grant access.
Frequently asked questions
What should I record?
Record client, version, UTC date, tool/schema revision and both activity IDs when you complete the workflow.