By Ira Bodnar, Ryze AI · Updated · Sources checked November 14, 2026
Quick answer
The main way to connect Microsoft Copilot to PostHog is the Ryze AI connector. Microsoft's pages show no Copilot chat window with a field for an MCP address, so the connector goes onto an agent: save a PostHog personal API key and host in Ryze AI, then on a Copilot Studio agent add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool with OAuth 2.0 and Dynamic discovery, and sign in to Ryze AI. The agent then holds 3 PostHog tools: one to read data and run HogQL, one to write and one to delete.
- In PostHog create a personal API key with the Query and Insight scopes, then in Ryze AI open Integrations, click Connect on PostHog and paste the key and host
- In Copilot Studio switch to the classic experience, open your agent, then Tools, Add a tool, New tool, Model Context Protocol
- Enter a name, a description and the URL, pick OAuth 2.0 with Dynamic discovery, then select Create and Next
- Create a new connection, sign in to Ryze AI, select Add to agent and ask a PostHog question in the test chat
Microsoft Copilot to PostHog at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: a hosted MCP server that a Copilot Studio agent takes as a tool. A Microsoft 365 Copilot declarative agent can take it as an action, a route not yet confirmed for Ryze AI |
| Server address | https://connector.get-ryze.ai/mcp, the same for every user |
| Where it goes in Copilot | On an agent. Classic experience: Tools > Add a tool > New tool > Model Context Protocol. New experience: Build tab > Tools > Add > Model Context Protocol (MCP). No chat window has a documented field for it |
| Sign-in | Copilot signs in to Ryze AI with OAuth 2.0 and Dynamic discovery. PostHog is joined once inside Ryze AI with a personal API key (starts with phx_) and a host, so Copilot never sees the key |
| PostHog tools | 3: 1 read, 1 write and 1 delete |
| Can the agent change PostHog | Yes, when the key has write scopes. A key with read scopes only keeps the agent read-only, because PostHog rejects any change |
| Projects per connection | One. Pick the Project after connecting; another project needs another Ryze AI workspace |
| Copilot plan | Microsoft's MCP pages name none. A trial cannot publish an agent, and the Copilot Studio for Teams plan lacks generative orchestration and Power Platform connectors |
| Ryze AI price | $89 a month for Paid Ads after a 7-day free trial. The connector itself costs nothing to add |
| PostHog's own option | A free hosted MCP server at https://mcp.posthog.com/mcp. Its pages name Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed, and no Microsoft Copilot product |
| Last checked | November 14, 2026, from Microsoft and PostHog pages. No PostHog call and no step inside Copilot was run |
Before you start
- A Copilot Studio agent or a Microsoft 365 Copilot declarative agent. This is a builder task, usually done by an agent maker or admin in a work or school tenant. Microsoft says Copilot Studio is available to all Microsoft 365 users for creating agents and actions. A Copilot Studio trial lets you create and test agents but cannot publish them, and Microsoft asks for a work or school account to sign up for it.
- A Copilot Studio plan that carries MCP. Microsoft lists four ways into Copilot Studio: a free user license that an admin assigns once the tenant owns a prepaid Copilot Credit pack, the Copilot Studio authors role, a Microsoft 365 Copilot license, or the trial. Microsoft documents that MCP access in Copilot Studio relies on Power Platform connectors, and its licensing page marks both Power Platform connectors and generative orchestration as not available in the Copilot Studio for Teams plan. Whether MCP tools run on the Teams plan is not documented, so test before you promise it to anyone.
- A PostHog personal API key. Create it in PostHog under Settings, Personal API keys, with read access to the project you want and the Query and Insight scopes. Add write scopes only for objects the agent may change. You also need the host: https://us.posthog.com, https://eu.posthog.com or your self-hosted address.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial; SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Connecting the connector is free, and the PostHog tools need an active plan or trial.
How to connect Copilot Studio to PostHog
Step 1 happens in PostHog and Ryze AI, steps 2 to 6 in Copilot Studio. The connector URL is the same for every user.
Save your PostHog key in Ryze AI
In PostHog go to Settings, Personal API keys, click Create key, grant read access to the project with the Query and Insight scopes, and copy the phx_ key. Then create a Ryze AI account or sign in, open Integrations, click Connect on the PostHog card, paste the key, enter the Host and click Continue. Pick the Project and click Save. Do this before you add the connector to Copilot.
Open the agent and start a new MCP tool
These steps are for the classic experience (the standard harness). New agents from the Copilot Studio home page run on the Microsoft Copilot harness, so switch first: select the three dots at the bottom of the home page side bar, then Open classic experience, which lasts for the session, or start the agent from Other ways to build. Open your agent and go to its Tools page. Select Add a tool, then New tool, then Model Context Protocol in the Create new section. The MCP onboarding wizard opens, which Microsoft calls the recommended way to add a server.
Fill in the server details
Server name: Ryze AI. Server description: a plain note on what the tools do, for example Reads PostHog events, insights, dashboards, flags and cohorts and runs HogQL queries. Microsoft says the agent orchestrator uses this description to decide when to call the server. Server URL: https://connector.get-ryze.ai/mcp.
Choose OAuth 2.0 with Dynamic discovery
Set the authentication type to OAuth 2.0 and the OAuth type to Dynamic discovery. The Ryze AI server supports dynamic client registration, so no client ID, secret or callback URL is typed. Microsoft calls Dynamic discovery the simplest of its three OAuth types. Select Create, then Next.
Create the connection and add the tool
On Add tool, select Create a new connection and complete the Ryze AI sign-in, or pick an existing connection. Microsoft's page stops at that button and does not show the sign-in window, and this step was not run for this guide. Then select Add to agent.
Ask a PostHog question in the test chat
MCP needs generative orchestration, which Microsoft says is on by default. Open the test chat panel and ask: List the dashboards in my PostHog project. If the PostHog tools do not run, check the troubleshooting list below.
The Ryze AI help article for PostHog covers the PostHog side of the connection. Microsoft's page on connecting an agent to an existing MCP server covers the Copilot Studio wizard, and its page on switching experiences shows how to open the classic experience. Checked November 14, 2026.
Microsoft 365 Copilot declarative agent
If your colleagues work in Microsoft 365 Copilot and not in Copilot Studio, the same URL can ride in a declarative agent as an MCP action. Microsoft documents this route in its Agents Toolkit walkthrough.
- Install Visual Studio Code and Microsoft 365 Agents Toolkit version 6.12.0 or later.
- Select the Agents Toolkit icon in the Activity Bar, then Create a New Agent/App, then Declarative Agent.
- Select Add an Action, then Start with an MCP Server, and enter https://connector.get-ryze.ai/mcp.
- Choose OAuth (with dynamic registration) as the authentication type, then pick a project location and an agent name. Nothing else is asked: no client ID, secret or scopes. Microsoft requires the authorization server to hand back a client secret at registration; whether the Ryze AI server does so for Microsoft was not checked.
- In the Accounts pane sign in to Microsoft 365 and look for Custom App Upload Enabled and Copilot Access Enabled. If either is missing, an admin has to allow custom app upload.
- In the Lifecycle pane select Provision, read the dialog, select Confirm and wait until the toolkit reports that provisioning finished.
- Open m365.cloud.microsoft/chat, find the agent in the Agents section of the sidebar (its name ends in dev), ask a PostHog question and select the Sign in button that carries the agent's name.
Microsoft says Agents Toolkit sets a new MCP plugin to dynamic tool discovery, so Copilot reads the server's tool list at run time and you add no tools by hand. Sideloading needs Upload custom apps switched on by an admin in the Teams admin center. The first time the agent uses the plugin, Copilot asks the person to allow or cancel. After that, tools that only read do not ask again, and tools that change data do.
Sources: Build a plugin for a declarative agent from an MCP server, dynamic client registration for plugins, Microsoft 365 Copilot extensibility requirements, plugin overview. Checked November 14, 2026.
New experience, admin connector and personal Copilot
Microsoft documents more places that accept an MCP address than the two above. Each changes who does the setup and how sign-in works, so find out which one your tenant uses first.
Copilot Studio, new experience
On the Microsoft Copilot harness the server is added from the agent's Build tab: Tools in the components panel on the right, Add beside the search bar, then Model Context Protocol (MCP). The Add MCP server page asks for Name, Description, Server URL and Authentication; select Add, review the tools Copilot Studio lists, then Save. Microsoft labels that how-to page preview, and its Authentication field lists no choices, so the page does not say whether Dynamic discovery is among them. For the PostHog tools through Ryze AI, the classic steps above are the documented route.
Getting the agent in front of colleagues
People reach a Copilot Studio agent from Teams and Microsoft Copilot after it has been published at least once and connected to the Teams and Microsoft Copilot channels. A trial license cannot publish, so a trial agent with the PostHog tools lives in the test chat panel only.
Admin route: a custom federated connector
A Global Administrator or AI Administrator can turn an MCP address into a connector in the Microsoft 365 admin center under Copilot > Connectors > Gallery > Create a new connector > Connect to MCP server. People with a Microsoft 365 Copilot license then connect it in Copilot Chat under Settings > Sources. Its sign-in methods are Microsoft Entra SSO, OAuth 2.0 with a client registered by hand in the Teams Developer Portal, or No Auth. Dynamic registration is not listed, and the Ryze AI connector registers clients through its register endpoint, so this route is unconfirmed for Ryze AI.
Copilot with a personal Microsoft account
Copilot on Copilot.com and Copilot Mobile with a personal account has four built-in connectors under Profile > Connectors: OneDrive, Outlook.com, Google Drive, and Gmail with Google Calendar and Contacts. Microsoft's support article does not mention MCP or a way to add your own, so a personal account has no documented place for PostHog through Ryze AI.
Microsoft Copilot and MCP in one table
| Topic | What Microsoft's pages say |
|---|---|
| Where the address is typed | In an agent or in an admin connector. Copilot Studio: the MCP wizard (classic) or the Add MCP server page (new). Microsoft 365 Copilot: a declarative agent action, a custom federated connector, or a plugin package manifest |
| Config files | None named for Copilot Studio, which is set up in the browser. Agents Toolkit writes ai-plugin.json in the agent project, and m365agents.yml holds isPKCEEnabled |
| Servers on your own computer | No route accepts a start command. Microsoft 365 Copilot must reach the server over the internet, and Microsoft points to a dev tunnel with a public HTTPS address for local work |
| Transport | Copilot Studio takes Streamable and dropped SSE after August 2025. Plugin packages and Cowork expect Streamable HTTP over HTTPS with TLS 1.2 or later |
| Sign-in, Copilot Studio wizard | None, an API key sent in a header or query parameter you name, or OAuth 2.0 as Dynamic discovery, Dynamic or Manual |
| Sign-in, declarative agent | Microsoft Entra SSO, dynamic client registration, the OAuth 2.0 authorization code flow or none. API keys are unsupported for MCP plugins, PKCE is on by default, and dynamic registration needs a client secret from the authorization server |
| Whose account a tool uses | In Copilot Studio a tool uses End user credentials by default, so each person signs in; Maker-provided credentials is the other choice. New-experience connections are saved per agent and per channel |
| Confirmation before a tool runs | Copilot Studio turns on every tool of a new server (Allow all). Declarative agents ask on first use and then before tools that change data. Federated connectors run read tools freely and keep write and delete tools at Needs approval |
| Plan and billing | The MCP how-to pages name no plan. Agents on the new experience are billed in Copilot Credits, charged for model tokens, the harness and tools, MCP servers included |
| Where servers are managed | Classic: select the server on the Tools page for Details, Tools, Resources and an Enabled toggle. New: the tools list on the Build tab. Declarative agents: Teams > Apps > Manage your apps |
| Admin controls | A data policy on Power Platform connectors also covers MCP servers. In the Microsoft 365 admin center, Agents > Tools > Registry can block a server, which turns off every tool it exposes |
Sources: adding an MCP server in the new experience, MCP in Copilot Studio, MCP tools and resources on an agent, agent tools and credentials, managing tools in the new experience, Teams and Microsoft Copilot channels, Copilot Credits, Copilot Studio access and browsers, plugin sign-in types, MCP servers in plugin packages, custom federated connectors, federated connector approvals, admin tool registry, Copilot connectors for personal accounts. Checked November 14, 2026.
Other AI clients
The same connector URL works in other MCP clients. Ryze AI has separate PostHog guides for them:
PostHog permissions
Two sign-ins are involved, and each limits what the agent can reach.
- PostHog key saved in Ryze AI
- A personal API key that starts with phx_, plus the host. PostHog says private endpoints give the same access as being logged in to PostHog, within the scopes and the project access set on the key. The key value is shown once at creation, and one user can hold up to 10 personal API keys.
- Ryze AI sign-in from Copilot
- The Copilot connection signs in to Ryze AI with OAuth 2.0. In Copilot Studio the tool runs on End user credentials unless the maker changes it, so each person who uses the agent makes a connection of their own. The agent reaches the one PostHog project picked in the Ryze AI workspace, and nothing else.
- Read-only option
- PostHog scopes are set on the key, not in Ryze AI. For a hard read-only setup, create the key with read scopes only. A change then fails because PostHog rejects it, whatever the agent is asked to do.
- Power Platform data policy
- Microsoft notes that a data policy on Power Platform connectors also regulates access to the MCP server and its tools. If a policy blocks the connector, ask your Power Platform admin.
Sources: Microsoft's MCP server and data policies note and the Ryze AI PostHog integration. Checked November 14, 2026.
PostHog scopes on the personal API key
PostHog gives each scope a read level and a write level, and write includes read. A request that needs a scope the key lacks fails with a 403 that names the missing scope. The Ryze AI help center asks for read access to the wanted projects and names the Query and Insight scopes. The other rows are what PostHog says each scope covers, and the third column marks whether Ryze AI names it.
| Scope | PostHog's description | Named by Ryze AI |
|---|---|---|
| query:read | Running SQL and insight queries on your project's data, plus event, session, and web vitals lookups. Read level only | Yes, needed for HogQL and saved insights |
| insight:read, insight:write | Insights, including their queries, results, and explanations, plus anomaly rates for trends insights | Read: yes. Write: only if the agent should change insights |
| dashboard:read, dashboard:write | Dashboards, including their tiles, text cards, widgets, and layout, and running the insights on them | No. Dashboard reads depend on this scope |
| feature_flag:read, feature_flag:write | Feature flags, including their release conditions, variants, payloads, and rollout history | No. Flag reads depend on this scope |
| cohort:read, cohort:write | Cohorts, including their filters, static member lists, calculation history, and where they are used | No. Cohort reads, creation and deletion depend on this scope |
| person:read, person:write | Persons and their properties, including updating, splitting, and deleting persons and their data | No |
| event_definition:read, event_definition:write | Event definitions, schemas, and property groups, including tags, verification, and generated type definitions | No. Event definition reads depend on this scope |
| project:read, project:write | Projects and their settings, including how data is ingested, plus creating and modifying projects | No |
The Ryze AI help center does not name the scopes for dashboards, flags, cohorts or event definitions, so a read of those objects works only when the key was created with them. Which OAuth scopes the Ryze AI connector hands a Copilot connection was not tested.
The key decides what the agent can change
PostHog counts API limits per personal API key and says requests made with OAuth or a logged-in session do not count against the personal API key limits. Because the key is saved in Ryze AI, anything else that uses the same key draws on the same allowance. These rows show which tool each job needs.
| What you ask the agent to do | Tool and key scope it needs |
|---|---|
| Run a HogQL query or read a saved insight | posthog__read with query:read and insight:read |
| List dashboards, flags, cohorts or event definitions | posthog__read with the scope for that object |
| Create or edit an insight or dashboard | posthog__write with insight:write and dashboard:write |
| Create a cohort | posthog__write with cohort:write |
| Create or update a feature flag | posthog__write with feature_flag:write |
| Delete an object, for example a cohort | posthog__delete with the write scope for that object. The deletion is irreversible |
PostHog's key can apply to the whole organization, to chosen projects or to all projects, and the scopes can be changed later. Ryze AI still connects one project per connection. Organization admins and owners can see every member's key that reaches the organization, with its scopes and last use, and GitHub secret scanning rolls an exposed phx_ key automatically and emails the user.
Out of reach on the default connection: a second project in the same workspace, any change while the key has read scopes only, and anything the key's scopes leave out. The PostHog MCP Server key preset is for PostHog's own server and its CLI, and the Ryze AI facts do not mention it.
Sources: PostHog API scopes, PostHog personal API keys, PostHog API overview. Checked November 14, 2026.
Removing access
To take PostHog away from a Copilot Studio agent, open its Tools page in the classic experience, hover over Ryze AI, select the three dots and Delete; to pause it instead, open the server, switch Enabled off and Save. In the new experience, select the X next to the server on the Build tab and then Remove. A sideloaded declarative agent is managed in Teams under Apps > Manage your apps. To stop Ryze AI reaching PostHog, click View on the PostHog card under Integrations in Ryze AI and disconnect it with the trash icon, then delete or roll the personal API key in PostHog.
What Copilot can do in PostHog
The Ryze AI connector exposes 3 PostHog tools: 1 read, 1 write and 1 delete. A Copilot agent calls them through the key you saved. The tool names come from the Ryze AI app source and were not seen in a live client, because no PostHog account was connected for this guide. Copilot Studio adds the whole server as one tool and switches every tool on through Allow all; turn Allow all off to switch single tools off.
| Tool | Type | What it does |
|---|---|---|
| posthog__read | Read | Reads PostHog data for the connected project (projects, insights, dashboards, feature flags, cohorts, persons, event definitions) and runs HogQL analytics queries. |
| posthog__write | Write | Creates or updates PostHog objects such as insights, dashboards, feature flags and cohorts. |
| posthog__delete | Delete | Deletes a PostHog object by path, for example a cohort. The deletion is irreversible. |
Two of the three tools change PostHog, and whether Copilot stops to ask depends on where the agent runs. In the classic experience, the Allow all switch above is how you keep the agent away from posthog__delete or posthog__write. Microsoft describes a per-tool setting, Ask the end user before running, that defaults to No, but it does not say the setting shows for an MCP server, so look for it on the Ryze AI tool. The new-experience pages describe only on and off switches. A Microsoft 365 declarative agent asks on first use and then before tools that change data, with allow once or always allow. The Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals and can be set to Approve write & delete or Manual approve, and scheduled tasks in Ryze AI run without an approval step. The firmest guard is the key: with read scopes only, PostHog rejects every change.
Limits in numbers
Three parties set limits on this route: PostHog's API, the Ryze AI tools and Copilot. PostHog counts most limits per personal API key and says it is not offering higher limits than these. No answer from a live call is cited here, because none was run.
| Limit | Figure or rule | Set by |
|---|---|---|
| Query endpoint | 2,400 per hour on the API overview. The queries page gives project-level figures: 2,400 per hour, 240 per minute, 3 queries running at once, 60 threads per query and 10 seconds of maximum execution time. A queued query may wait up to 30 seconds. Some older accounts sit on 120 queries per hour | PostHog |
| Hourly read budget | Queries made with a personal API key draw on an hourly read budget per project, counted in bytes read. When it is used up the answer is HTTP 429 with the code api_queries_budget_exceeded and a Retry-After header. Cached results still work. PostHog publishes no byte figure | PostHog |
| Analytics endpoints | 240 per minute and 1,200 per hour per personal API key, for calculating insights, retrieving persons and session recordings | PostHog |
| Other create, read, update and delete endpoints | 480 per minute and 4,800 per hour per personal API key | PostHog |
| Rows per query | By default an API query returns up to 100 rows, and with your own LIMIT up to 50,000. OFFSET returns HTTP 400 for personal API keys; use keyset pagination on timestamp. PostHog calls the query endpoint not a supported export mechanism | PostHog |
| HogQL through Ryze AI | Queries need a time window and a row limit of 1,000 at most. This is a Ryze AI rule from its facts, not a PostHog page | Ryze AI |
| PostHog's own MCP server, for comparison | 480 requests per minute and 4,800 per hour, counted per credential; opening a session and listing tools count as requests. This applies to mcp.posthog.com, not to the Ryze AI connector | PostHog |
| Tools on a Copilot Studio agent | Up to 128 with generative orchestration, and Microsoft suggests 25 to 30. The Ryze AI server is added as one tool; Microsoft does not say whether the 3 PostHog tools inside it count toward 128 | Microsoft, classic experience |
| MCP servers in one conversation | An agent can hold several, but only a capped number run in one conversation and the rest are skipped for that turn. Microsoft gives no figure | Microsoft, new experience |
| Plugins in a declarative agent | Up to 5 plugins always go into the prompt, and answers may get worse above 10 tools in one plugin. The PostHog tools stay far below that | Microsoft 365 Copilot |
| Tool call time in plugin packages | A tool call should finish in under 30 seconds, which matters for a long HogQL query. Microsoft names this for plugin packages and Cowork | Microsoft |
| Tool list after a change | Copilot Studio picks up server changes by itself. After a custom connector is republished, tool changes can take about 12 to 24 hours to show, with no manual refresh | Microsoft |
Sources: PostHog API rate limits, PostHog query endpoint limits, PostHog MCP server FAQ, Copilot Studio tool limits, MCP servers per conversation, declarative agent plugin limits, Copilot Studio MCP troubleshooting, tool call time in plugin packages, Ryze AI PostHog integration. Checked November 14, 2026.
No PostHog call was run for this guide, so there is no table of tested calls.
First 3 prompts to run
Each answer comes from your own PostHog project, so this page describes what comes back and shows no sample numbers. Add the prompts to the agent's instructions or paste them into the test chat.
1. Daily pageviews for the last week
Run a HogQL query that counts pageviews per day for the last 7 days in my PostHog project, with a time window and no more than 1,000 rows.
Tools used: posthog__read
What comes back: One row per day with a pageview count. The key needs query:read.
2. Traffic by UTM source
Break down last month's sessions by UTM source with a HogQL query over sessions, so I can see which campaigns sent traffic.
Tools used: posthog__read
What comes back: A table of UTM sources with a session count for each, from the sessions in your project.
3. Read a saved funnel
Open my saved signup funnel insight and tell me how many people reach each step.
Tools used: posthog__read
What comes back: The funnel's steps with the number of people at each one. The key needs insight:read and query:read.
Ryze AI has not tested this connection in Copilot Studio or Microsoft 365 Copilot, and no PostHog call was run for this guide. The steps follow Microsoft's documentation and the connector's OAuth metadata, which supports dynamic client registration. Report anything that differs to Ryze AI support.
10 jobs to hand to a Copilot agent
Ten jobs a Copilot agent with the Ryze AI tool can take on, each matched to its tool. None was run, from Copilot or anywhere else. The first column of conditions follows the key: the Ryze AI help center names the Query and Insight scopes, so jobs on other objects depend on the scopes you gave the key.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| Dashboard list | List the dashboards in the project with their names, so I can name the right one later. | posthog__read | Only if the key has dashboard:read. Not tested |
| Daily pageviews | Count pageviews per day for the last 7 days with a HogQL query. | posthog__read | Yes, with query:read. Not tested |
| Campaign traffic | Break down last month's sessions by UTM source with a HogQL query over sessions. | posthog__read | Yes, with query:read. Not tested |
| Funnel check | Read the saved signup funnel and report how many people reach each step. | posthog__read | Yes, with insight:read and query:read. Not tested |
| Flag review | List the feature flags with their current rollout settings before a launch. | posthog__read | Only if the key has feature_flag:read. Not tested |
| Cohort list | List the cohorts and say what defines each one. | posthog__read | Only if the key has cohort:read. Not tested |
| Event check | List the event definitions so I know which events exist before I build a report. | posthog__read | Only if the key has event_definition:read. Not tested |
| New insight and dashboard | Create a trends insight for landing page signups and add it to a new campaign dashboard. | posthog__write | No. Needs a key with insight:write and dashboard:write |
| Campaign cohort | Create a cohort of people who arrived from one campaign. | posthog__write | No. Needs a key with cohort:write |
| Clean-up | Delete the old test cohort I name. This cannot be undone. | posthog__delete | No. Needs a key with cohort:write |
5 ways to connect Microsoft Copilot to PostHog
Five ways can bring PostHog into a Microsoft Copilot agent. This guide uses the Ryze AI connector as the main way: Copilot Studio's wizard takes its address with Dynamic discovery, the PostHog key stays inside Ryze AI, and no key is pasted into Copilot. None of the five was run inside Copilot for this guide. The setup column says how each one is meant to reach an agent.
| Way | Runs where | Setup in Copilot | What it reaches in PostHog | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI at one address for every user | Copilot Studio: MCP wizard with the connector URL and OAuth 2.0 Dynamic discovery, then Create a new connection. Microsoft 365 Copilot: a declarative agent action with OAuth (with dynamic registration), not confirmed for Ryze AI | 3 tools: reads of insights, dashboards, flags, cohorts, persons and event definitions, HogQL queries, writes to insights, dashboards, flags and cohorts, and a delete tool. One project per connection | Paid Ads $89 a month after a 7-day free trial; SEO Starter $129 a month; Agency $279 a month |
| PostHog's own hosted MCP server | Hosted by PostHog at https://mcp.posthog.com/mcp over streamable HTTP; sign-in routes to the US or EU region of the account | Copilot Studio's wizard takes a URL, and PostHog documents OAuth, or a personal API key with the MCP Server preset sent as Authorization: Bearer. Copilot Studio's API key option sends a key in a header you name; whether it can carry the Bearer prefix, and whether PostHog's OAuth works with Dynamic discovery, were not checked. PostHog's setup pages name no Microsoft Copilot product | 1,284 tools in 78 categories on posthog.com/mcp.md, built November 14, 2026, covering product analytics, session replay, flags, experiments, error tracking, surveys, SQL, the data warehouse and more. Read and write. A ?readonly=true setting removes tools that create, update or delete, and ?features= or ?tools= narrows the list | Free to connect and call, though some tools use LLMs inside PostHog and may bill as PostHog AI spend |
| Windsor.ai (Windsor MCP) | Hosted by Windsor.ai; PostHog is a data source and Windsor MCP a destination | Windsor.ai's pages name Copilot Agent among the assistants it serves. The setup guide read covers ChatGPT, so the Copilot steps were not checked | A PostHog connector with 101 fields: annotations, cohorts, events, feature flags, insights, persons and projects. No tool count is printed, and the pages do not say how PostHog is authenticated or how fresh the data is | Forever Free after a 30-day trial: 1 user, 1 data source, 1 account, data from the past 30 days. Basic is $23 per month, or $19 per month billed yearly |
| Coupler.io | Hosted export service that syncs PostHog data to an AI destination on a schedule | Coupler.io lists Copilot and Custom MCP among AI destinations for PostHog. You enter a PostHog private API key and the host, choose an entity and a start date, then pick the destination. That pairing was not tried | Exports of 7 entities: Projects, Cohorts, Feature flags, Persons, Events, Annotations and Insights. The AI tool reads synced data rather than querying PostHog directly | Free plan: 1 account, 1 source, 1 destination, manual refresh, 100 rows per run. Starter is $32 per month, or $24 billed yearly |
| Composio | Hosted by Composio at https://connect.composio.dev/mcp over Streamable HTTP, the transport Copilot Studio accepts | Add the address, then Authenticate and Allow access. PostHog itself is joined with your own API key. Composio's list of assistants does not name Microsoft Copilot, so the Copilot route was not checked | A Posthog toolkit listed with 686 tools and 11 triggers. A second toolkit named PostHog MCP lists 1 tool | Free $0 with $2 in credits once and app tool calls stopping at 10,000 a month. Standard is $18 per seat per month |
With a hosted way your PostHog data passes through that vendor, and Microsoft says you are responsible for the tools and resources you reach through a non-Microsoft MCP server in Copilot Studio. Composio's toolkit page also says its free plan includes 100,000 tool calls a month, which differs from its pricing page; the pricing page figure is used here.
Options that do not fit a Copilot agent
- Zapier MCP. Zapier's PostHog page lists 1 action, Capture Event, and the integration page adds 1 trigger. No read of insights, dashboards, flags or cohorts is listed, so it cannot answer an analytics question. Each successful tool call uses 2 tasks from your Zapier plan.
- Pipedream MCP. A hosted server at https://mcp.pipedream.net/v2 with 10 PostHog actions as tools, among them List Project Insights, Create Query (a HogQL query that returns results) and Get Cohorts. PostHog is joined with an API key, and the page shows no price. Its pages read for this guide do not name Copilot.
- viaSocket MCP and Improvado MCP. viaSocket lists 12 PostHog actions as tools and names ChatGPT, Claude and Cursor. Improvado describes a PostHog server with read and write access for Claude, Cursor and other agents, with no tool count or price on the page. Neither names Copilot.
- PostHog's wizard and plugins. The command npx @posthog/wizard mcp add detects Claude Code and Codex and writes the connection into them, and the PostHog AI plugin targets Claude Code, Cursor, Gemini and Codex. Both configure a coding tool on your computer, and Copilot Studio has no field for a start command.
- A custom federated connector pointed at Ryze AI. This is the admin route in the section on other Copilot surfaces. None of its three sign-in methods is dynamic registration, which is how the Ryze AI connector signs clients up, so it stays unconfirmed for Ryze AI.
Which one to pick
Pick the Ryze AI connector when one Copilot Studio agent should read PostHog, run HogQL and, if you allow it, edit insights, dashboards, flags and cohorts, with the key kept inside Ryze AI. The caveats are that the route has not been run inside Copilot, that it needs a Ryze AI plan once the trial ends, and that it reaches one PostHog project and 3 tools. Pick PostHog's own server when you need session replay, experiments, error tracking or the data warehouse in the same agent, and accept that its pages name no Microsoft Copilot product and that its 1,284 tools sit well above the 25 to 30 Microsoft suggests per agent. Coupler.io fits scheduled, read-only exports and has a free plan, Windsor.ai fits a team that wants PostHog beside many other sources, and Composio is a hosted option whose Copilot route is untested.
Sources: PostHog MCP server overview, posthog.com/mcp, PostHog MCP tools, PostHog AI wizard, PostHog/ai-plugin, Windsor.ai PostHog fields, Windsor MCP, Windsor.ai pricing, Coupler.io PostHog source, Coupler.io pricing, Composio PostHog toolkit, Composio pricing, Zapier MCP for PostHog, Pipedream MCP for PostHog, viaSocket MCP for PostHog, Improvado MCP for PostHog, Copilot Studio MCP guide, third-party MCP servers in Copilot Studio, custom federated connectors, Ryze AI PostHog integration. Checked November 14, 2026.
Copilot, PostHog and MCP: dates that matter
| Date | What happened |
|---|---|
| March 19, 2025 | Microsoft announced MCP support in Copilot Studio. The first release used the SSE transport; a later post calls it a public preview. |
| May 29, 2025 | MCP in Copilot Studio reached general availability, with the tool list on the server settings page, streamable transport and tracing of which server and tool ran. |
| August 2025 | Copilot Studio stopped supporting SSE for MCP; Streamable is the only supported transport. Microsoft gives no exact day. |
| December 15, 2025 | Microsoft announced general availability of MCP in declarative agents for Microsoft 365 Copilot, built in Agents Toolkit with Add Action, Start with an MCP server. |
| February 27, 2026 | PostHog's changelog announced a PostHog connector for Claude, and the same day Manage cohorts through PostHog MCP. |
| August 27, 2026 | PostHog's changelog: Simplify MCP editor login, which hands OAuth sign-in to the editor in Claude Code and Codex setups. |
| September 2, 2026 | A Microsoft Copilot blog post announced general availability of the GitHub Copilot harness in Copilot Studio, since renamed the Microsoft Copilot harness, with MCP servers as tools. Microsoft's how-to page for adding a server on that harness still carries a preview label. |
| October 1, 2026 | PostHog's changelog: longer-lived MCP connections. Clients with non-rotating refresh tokens stay connected instead of asking for a new authorization after roughly 67 days. |
| October 22, 2026 | PostHog's changelog: simpler MCP installations. The wizard detects Claude Code and Codex, and a separate flow handles browser and account-based clients such as ChatGPT and Claude. |
| October 27, 2026 | The Microsoft 365 Copilot release notes list, under this date, admins creating custom MCP connectors in the Microsoft 365 admin center. Microsoft's roadmap item gives an earlier availability month, February 2026. |
| November 14, 2026 | posthog.com/mcp.md, built on this day, counts 1,284 tools in 78 categories for PostHog's own server. |
Sources: Microsoft Copilot blog, March 19, 2025, Microsoft Copilot blog, May 29, 2025, SSE support ended after August 2025, Microsoft 365 Developer Blog, December 15, 2025, Microsoft Copilot blog, September 2, 2026, adding an MCP server in the new experience, Microsoft 365 Copilot release notes, Microsoft 365 roadmap item 501585, PostHog changelog, February 27, 2026, PostHog changelog, August 27, 2026, PostHog changelog, October 1, 2026, PostHog changelog, October 22, 2026, posthog.com/mcp. Checked November 14, 2026.
How this guide was tested
No PostHog call was run for this guide, so there is no tested-call table and no list of messages captured from a live answer. What was done, on November 14, 2026, is reading: Microsoft's pages, PostHog's pages, vendor pages and two public files of the Ryze AI connector.
| What was run | What came back |
|---|---|
| The connector's authorization server file | Requested once on November 14, 2026 and read for its list of client authentication methods. No client was registered and no sign-in was started. |
| The connector's protected resource file | Requested once on the same day; it answered with HTTP 200. Only the status was noted. |
| Microsoft's Copilot Studio and Microsoft 365 Copilot pages | Read on the same day for every setup step, limit, plan note and date used here. |
| PostHog's MCP, API, scope, query and changelog pages | Read on the same day for every PostHog scope, limit, date and the details of PostHog's own server. |
| Vendor pages for Windsor.ai, Coupler.io, Composio, Zapier, Pipedream, viaSocket and Improvado | Read on the same day for the comparison. Their tool counts and prices are as the pages printed them. |
Not run for this guide: anything inside a Microsoft product and anything against PostHog. No Copilot Studio agent was created, no MCP tool was added, no Agents Toolkit project was built, no admin center connector was set up, and no Ryze AI sign-in happened from Copilot. No PostHog test account was connected, so the three PostHog tool names come from the Ryze AI app source and were not seen in a live client, and no HogQL query, insight, dashboard, flag or cohort was read or changed. Those steps follow Microsoft's and Ryze AI's documentation as read on November 14, 2026.
Errors and fixes
No error message was captured from a live answer for this guide, because no PostHog call was run. The PostHog entries below come from PostHog's documentation and say so; each can be checked on the page named under the list.
- There is no place to paste the URL in Copilot chat
- Microsoft's pages show no field for an MCP address in a Copilot chat window. Add the URL as a tool on a Copilot Studio agent or build a declarative agent in Agents Toolkit. An admin can also create a custom federated connector in the Microsoft 365 admin center, but that route was not confirmed for Ryze AI.
- The Tools page or the New tool button is missing
- The agent runs on the new experience, where tools sit on the Build tab. Open the classic experience from the three dots at the bottom of the home page side bar, or create the agent with Other ways to build.
- I cannot publish the agent
- A Copilot Studio trial lets you create and test agents but not publish them. Use the test chat panel, or move to a plan that can publish.
- Model Context Protocol or connectors are missing on the Teams plan
- The Copilot Studio for Teams plan does not include Power Platform connectors or generative orchestration, and MCP access relies on connectors. Ask your admin about a standalone Copilot Studio subscription.
- The connector is blocked
- A Power Platform data policy that regulates connectors also regulates the MCP server, and a blocked tool shows as disabled in the Add tool panel. Ask your Power Platform admin to allow it. A tool that an organization policy limits to certain people may also wait for an admin to approve the request under Agents > Tools > Requests in the Microsoft 365 admin center.
- Agents Toolkit says Custom App Upload is not enabled
- Sideloading needs Upload custom apps turned on by an admin in the Teams admin center. Ask your admin, then reload the Accounts pane.
- The declarative agent sign-in fails
- Microsoft's dynamic registration for declarative agents needs the authorization server to issue a client secret, and registration without one is not supported yet. This was not checked for the Ryze AI server, so use the Copilot Studio route if the sign-in does not complete.
- The agent never calls the PostHog tools
- Microsoft says the orchestrator uses the server description to decide whether to call the server. Rewrite the description to say what the tools do, such as reading PostHog events and dashboards, and check that generative orchestration is on.
- The tools return a subscription message or no data
- The PostHog tools need an active Ryze AI plan or free trial, and PostHog must show as connected under Integrations in Ryze AI. If the connector was added before PostHog was connected, remove it from the agent, add it again and start a new test chat.
- PostHog answers 401 with Invalid Personal API key.
- From PostHog's documentation, not from a test: the key is wrong, deleted or rolled. Create a new key in PostHog and replace it on the PostHog card in Ryze AI.
- PostHog answers 403 and names a missing scope
- From PostHog's documentation: the key lacks the scope the request needs, for example dashboard:read for a dashboard list. Add the scope to the key in PostHog.
- PostHog answers 429 with api_queries_budget_exceeded
- From PostHog's documentation: the project's hourly read budget for personal API key queries is used up. Cached results still work, and the Retry-After header says when to try again.
- PostHog answers 400 on OFFSET
- From PostHog's documentation: OFFSET pagination on the query endpoint is rejected for personal API keys. Ask the agent to page with a timestamp filter and a LIMIT instead.
- A change is refused
- The key may hold read scopes only. PostHog scopes are set on the key, not in Ryze AI.
- I need a second project
- Ryze AI holds one PostHog project per connection. Use another workspace for the other project, or disconnect with the trash icon on the card and connect again.
Sources: PostHog API, PostHog API scopes, PostHog queries, Copilot Studio MCP troubleshooting. Checked November 14, 2026.
Terms on this page
- MCP (Model Context Protocol)
- An open standard through which an AI model reaches outside data and applications. Copilot Studio adds an MCP server to an agent as a tool, and PostHog runs its own MCP server too.
- Classic and new experience
- The two ways Copilot Studio builds agents. Microsoft's pages call the classic one the standard harness and the new one the Microsoft Copilot harness. The setup steps in this guide use the classic one.
- Dynamic discovery
- A Copilot Studio OAuth 2.0 option for servers that support dynamic client registration: Copilot Studio finds the sign-in endpoints and registers itself, so nobody types a client ID.
- Declarative agent
- A Microsoft 365 Copilot agent built from a manifest, here in Agents Toolkit, that can carry an MCP server as an action.
- Personal API key
- A PostHog key that starts with phx_ and authenticates the private API as your own user. You choose its scopes, and one user can create up to 10.
- HogQL
- PostHog's SQL, a wrapper around ClickHouse SQL, used to query events, persons and sessions.
- Insight
- PostHog's main building block for product analytics, such as a trends chart, a funnel or a retention table.
Sources: PostHog MCP server, Copilot Studio experiences, Dynamic discovery, declarative agents with MCP, personal API keys, HogQL, insights. Checked November 14, 2026.
Frequently asked questions
How to connect Copilot to PostHog?
Ryze AI is the best way to connect Microsoft Copilot to PostHog for an agent that should read analytics and, if you allow it, edit insights and flags, though it has not been run inside Copilot and needs a Ryze AI plan or trial. Save a PostHog personal API key in Ryze AI, then add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool on your Copilot Studio agent with OAuth 2.0 and Dynamic discovery, select Create and Next, and create the connection.
Is there a PostHog connector for Copilot?
Microsoft's pages list no PostHog connector, and PostHog's setup pages name no Microsoft Copilot product. Copilot Studio can add an existing MCP server as a tool, and the Ryze AI connector is a hosted server you can add that way. Copilot Studio's MCP tab lists servers already published in your organization; that list needs a signed-in tenant and was not opened for this guide.
Is there a Copilot PostHog MCP server I can use?
Yes, two hosted ones can be tried. The Ryze AI connector at https://connector.get-ryze.ai/mcp gives an agent 3 PostHog tools. PostHog's own server at https://mcp.posthog.com/mcp is free and lists 1,284 tools, but its pages name Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed, not Microsoft Copilot. Neither was run inside Copilot for this guide.
Can I add a PostHog connector in Microsoft 365 Copilot without Copilot Studio?
Microsoft documents routes that skip Copilot Studio: a developer can add the connector URL as an action in a declarative agent built with Agents Toolkit, or an admin can create a custom federated connector in the Microsoft 365 admin center. The declarative agent route needs a client secret from dynamic registration, which was not checked for Ryze AI, and the admin route lists no dynamic registration, so neither is confirmed for the Ryze AI connector.
Can I paste an MCP URL into the Copilot chat app?
No. None of Microsoft's pages shows a Copilot chat window that takes an MCP address. The URL goes in Copilot Studio on an agent's Tools page or Build tab, in a declarative agent built with Microsoft 365 Agents Toolkit, or in an admin's custom federated connector that people then turn on under Settings > Sources.
Which Copilot plan do I need?
Microsoft says Copilot Studio is available to all Microsoft 365 users for creating agents and actions. A trial can create and test but not publish. The Teams plan lacks Power Platform connectors, which MCP access relies on, so plan for a standalone Copilot Studio subscription. For Microsoft 365 Copilot declarative agents an admin must allow custom app upload.
What PostHog permissions do I need?
A personal API key with read access to the project and the Query and Insight scopes. Reads of dashboards, flags, cohorts or event definitions depend on the scopes you gave the key. Add write scopes only for objects the agent should change.
Can Copilot change my PostHog project or delete things?
Through Ryze AI, yes, when the key has write scopes. posthog__write creates or updates insights, dashboards, feature flags and cohorts, and posthog__delete removes an object, which is irreversible. For a read-only setup, create the key with read scopes only; PostHog then rejects every change.
Does the Ryze AI connector work with Copilot Studio?
The connector is a remote MCP server with OAuth that supports dynamic client registration, which matches Microsoft's Dynamic discovery option. Ryze AI has not tested it in Copilot Studio or Microsoft 365 Copilot, so try it on a project you can afford to experiment with.
Can I connect more than one PostHog project?
Not in one workspace. Ryze AI holds one PostHog project per connection, picked after connecting. Another project can live in another Ryze AI workspace, and one Claude or ChatGPT connection can cover up to 20 workspaces. How a Copilot connection picks a workspace was not tested.
Does it work with EU Cloud or self-hosted PostHog?
Yes. When you save the key in Ryze AI you enter the host: https://us.posthog.com for US Cloud, https://eu.posthog.com for EU Cloud, or your own address when self-hosted.
Which transport does Copilot Studio support?
Microsoft says Copilot Studio supports the Streamable transport for MCP and no longer supports SSE after August 2025.
How much does it cost?
Adding the connector costs nothing, but the PostHog tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year. Copilot Studio licensing is set by Microsoft, and PostHog's own pricing applies to your data.
How do I disconnect PostHog from Copilot?
Remove the Ryze AI tool from the agent in Copilot Studio. To cut Ryze AI off from PostHog, click View on the PostHog card under Integrations in Ryze AI and disconnect with the trash icon, then delete the personal API key in PostHog.