How to use PostHog with Copilot Studio
You want PostHog inside Copilot Studio so it can investigate a drop in conversion, review an experiment before rollout, triage production errors, and maintain product analytics dashboards — without you copy-pasting between tabs. Here is the whole setup, once.
Create your PostHog gateway
The gateway is the thing Copilot Studio connects to, and it is where you decide which PostHog tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your PostHog tools
In the dashboard, create a gateway and pick the PostHog tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Copilot Studio
Needs a Microsoft 365 subscription with access to Copilot Studio, plus an Arcade API key.
-
Add an MCP tool to your agent
In Copilot Studio, open your agent → Tools → Add a tool → Model Context Protocol → New tool.
-
Point it at your gateway
Give the server a name and description, put your gateway URL in Server URL, set Authentication to OAuth 2.0 and Type to Dynamic discovery.
-
Authorize and try it out
Saving redirects you to Arcade to approve access. Then start a conversation and use your PostHog tools — Arcade authorizes each service just in time.
Full Copilot Studio guide in the docs steps verified 2026-08-13
Get started with these PostHog prompts
Copilot Studio can now act on your PostHog account. Click a prompt to copy it.
Use scoped credentials and tool permissions to control which PostHog actions an agent can take. Pair it with Contextual Access policies so an agent can analyze product data without being allowed to change a feature flag, delete an insight, or archive an experiment.