By Ira Bodnar, Ryze AI · Updated · Connector tested November 20, 2026
Quick answer
The main way to connect Muse to PostHog is the Ryze AI connector. Create a personal API key in PostHog and paste it, with your host, into the PostHog card in Ryze AI, then ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, follow its guided setup and sign in to Ryze AI when the link arrives. The key stays in Ryze AI, and Muse reaches PostHog through 3 tools.
- In PostHog open Settings, Personal API keys and create a key with the Query and Insight scopes
- In Ryze AI open Integrations, click Connect on PostHog, paste the key, enter the host and pick the Project
- In a Muse chat, ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp
- Open the sign-in link Muse sends, choose the workspace and click Allow connection
Muse to PostHog at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, created by asking Muse in a chat |
| Server address | https://connector.get-ryze.ai/mcp |
| Where Muse is available | The US and Canada, per Meta |
| Sign-in | A link Muse sends back opens the Ryze AI sign-in, where you pick workspaces and click Allow connection. PostHog itself is reached with a phx_ personal API key and a host, both saved in Ryze AI |
| PostHog tools | 3: 1 read, 1 write and 1 delete (posthog__read, posthog__write, posthog__delete) |
| Can Muse change PostHog | Only if the key has write scopes. With read scopes only, PostHog rejects any change. Meta says Muse does not take many important actions without approval by default |
| Other data in the same chat | Platforms connected in the same Ryze AI workspace use the same URL |
| Muse plan | Meta's help and newsroom pages reviewed name no plan for custom connectors |
| Ryze AI price | Paid Ads at $89 per month with a 7-day free trial. Connecting is free |
| PostHog's own option for Muse | PostHog hosts an MCP server at https://mcp.posthog.com/mcp. Its docs list no Muse setup, and the steps for Muse are untried |
| Last tested | Connector November 20, 2026; PostHog pages November 14, 2026; no PostHog call and nothing run inside Muse |
Before you start
- A Muse account in the US or Canada. Meta says Muse is offered in those two countries only. The help and newsroom pages reviewed name no plan for custom connectors, so none is claimed here.
- A PostHog personal API key. The key acts as the user who created it, within the scopes and projects set on it. It needs read access to the wanted projects, including the Query and Insight scopes. Add write scopes only if Muse should change insights, dashboards, flags or cohorts.
- Your PostHog host. https://us.posthog.com for US Cloud, https://eu.posthog.com for EU Cloud, or your own address when self-hosted.
- A Ryze AI workspace on a plan or trial. PostHog tools run on Paid Ads at $89 per month, which starts with a 7-day free trial, and on SEO Starter or Agency. Connecting costs nothing, but without a plan or trial the connector can only list workspaces and connect platforms.
How to connect Muse to PostHog
PostHog and Ryze AI take the first two steps, and Muse the other four. Everyone uses the same connector URL.
Create a personal API key in PostHog
In PostHog, go to Settings, then Personal API keys, and click Create key. Grant read access to the projects you want, with the Query and Insight scopes, and add write scopes only for objects Muse should change. Copy the phx_ key right away, because PostHog shows the value once.
Connect PostHog in Ryze AI
Create a Ryze AI account or sign in, open Integrations, click Connect on the PostHog card, paste the key, enter the Host (US Cloud, EU Cloud or your self-hosted URL) and click Continue. Then pick the Project and click Save. One connection holds one PostHog project.
Ask Muse to create the custom connector
In a Muse chat on the web or in the app, ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp. The Ryze AI page at ryze.ai/muse has a ready-made message you can paste. Meta describes no settings field for a server URL, so the chat request is the route.
Follow Muse's guided setup
Muse walks you through the setup and sends back a sign-in link. Meta says setup can involve retrieving API information from the service, and Muse keeps the credentials in its Secure Credentials Store.
Sign in to Ryze AI and allow the connection
Open the link, sign in on the Ryze AI page, choose the workspace that holds your PostHog connection and click Allow connection.
Check approvals and ask your first question
Muse settings control how much it does without asking. Then ask: List the dashboards in my PostHog project by name. To change or remove the connector later, open Settings, then Connectors in Muse.
The Ryze AI help center page for PostHog covers the PostHog side of the connection, and Meta describes custom connectors in its Muse help article.
Sources: Meta help: Muse connectors, Ryze AI Muse page. Checked November 8, 2026. Ryze AI PostHog guide. Checked November 14, 2026.
Where Muse is available
Meta introduced Muse for small businesses in a September 2026 newsroom post and says Muse is available in the US and Canada. The post lists connectors to services such as Shopify, Slack and Stripe and says custom connectors cover services Meta does not support yet. PostHog was not among the services named in that post.
Muse is a chat assistant with no code editor or command line side in the pages reviewed, so there is one place to connect: the chat on the web or in the app. If you work in a code editor, the guides linked in Related guides below cover Cursor, Claude Code and other clients.
Muse and connectors: the facts in one table
| Topic | What Meta and Ryze AI say |
|---|---|
| How a connector is created | By asking Muse in a chat to create a custom connector, then following the guided setup it starts |
| Server URL field | None described. Meta's pages never mention MCP or a field for a server address |
| Where Ryze AI's connector details come from | The Ryze AI page at ryze.ai/muse, updated September 24, 2026: MCP over HTTP with an OAuth sign-in. Meta's pages do not confirm this, and it was not verified independently |
| Credentials | Muse stores them in its Secure Credentials Store, per Meta |
| Approval | By default Muse does not take many important actions without approval. Meta says the approval behavior is changed in Settings |
| Meta's newsroom on actions | Nothing publishes, sends or spends without your approval |
| Reviewing connectors | Meta does not review custom connectors or how they use data |
| Where connectors are managed | Muse Settings, then Connectors |
| Availability | The US and Canada |
| Plan | Meta's pages reviewed name none for custom connectors |
Sources: Meta help: Muse connectors, Meta newsroom: Muse for small business, Ryze AI Muse page. Checked November 8, 2026.
Claude and ChatGPT
Other MCP clients accept the same URL, and the PostHog connection made in Ryze AI stays as it is.
Claude
Add the same URL under Customize, Connectors, Add custom connector, then pick the workspace and start a new chat. Claude keeps the tool list from the moment you add the connector, so if you connected PostHog in Ryze AI afterwards, remove the connector, add it again and open a new chat. PostHog also lists its own connector in the Claude directory.
ChatGPT
OpenAI lists full custom MCP support for Business and Enterprise/Edu workspaces on ChatGPT web, with Pro limited to read and fetch permissions. The steps are in the ChatGPT guide linked below. PostHog also lists a plugin for ChatGPT.
PostHog permissions
PostHog access comes from one personal API key, and Muse adds its own approval setting. Meta says it does not review custom connectors. Three things decide what Muse can touch.
- Who can connect
- You can, from a Muse chat. In PostHog, whoever creates the key decides its scopes, and the key acts as that user. Ryze AI uses whatever the key allows.
- Which project
- One connection holds one PostHog project, picked after connecting. PostHog is not on the Ryze AI help center list of platforms that support several accounts. To switch, click View on the card, disconnect with the trash icon and connect again. Another project can live in another workspace.
- What the key covers
- Read scopes let Muse read and run queries. Write scopes let it create or change insights, dashboards, feature flags and cohorts, and the delete tool removes those objects. A key with read scopes only keeps Muse read-only, because PostHog rejects any change.
The access layers between Muse and PostHog
Several sign-ins and keys sit between a Muse chat and your PostHog project. Read the table from Muse down to PostHog.
| Layer | What it allows | Where it is set |
|---|---|---|
| Muse to the Ryze AI connector | A sign-in on the Ryze AI page that Muse's link opens. The connector offers two scopes, mcp:read and mcp:write | The sign-in link from Muse |
| Ryze AI workspace | The workspace you allow there | The Allow connection screen |
| Ryze AI to PostHog | A personal API key that starts with phx_, plus the host. It needs read access to the wanted projects, including the Query and Insight scopes | PostHog Settings, Personal API keys, then the PostHog card in Ryze AI |
| Read and write levels | Each PostHog scope has a read level and a write level. Per PostHog, write access includes read access and lets the key view, create, change and delete the data | The key's scope list in PostHog, changeable later |
| Missing scope | A request that needs a scope the key lacks fails with a 403 that names the missing scope | PostHog |
| Muse approvals | By default Muse does not take many important actions without approval | Muse Settings |
The Ryze AI help center names the Query and Insight scopes and read access to the wanted projects. It names no scope for dashboards, flags, cohorts or event definitions, and PostHog has a separate scope for each. Whether listing those objects works with only the two named scopes was not tested, so if a list call fails, check the 403 message for the missing scope.
What the connection does not include
- Write scopes. insight:write, dashboard:write, feature_flag:write and cohort:write are left off the key unless you add them. Without them Muse can read and cannot change those objects.
- A second project. One connection holds one project. Another project needs another workspace or a reconnect.
- OAuth to PostHog. The Ryze AI facts describe a key and host, with no PostHog sign-in for this connection.
- The MCP Server key preset. PostHog's own server and CLI use that preset. The Ryze AI connection uses a personal API key with the scopes above.
- Session recordings, experiments, surveys and error tracking. The Ryze AI facts name insights, dashboards, flags, cohorts, persons, event definitions, projects and HogQL queries, so this guide claims none of those four.
Sources: PostHog personal API keys, PostHog API scopes, PostHog API overview, PostHog HogQL queries, Ryze AI PostHog guide. Checked November 14, 2026. Meta help: Muse connectors, Meta newsroom: Muse for small business. Checked November 8, 2026.
Removing access
To cut access, disconnect the connector in Muse under Settings, then Connectors, or delete the key in PostHog under Personal API keys. To switch project or key, click View on the PostHog card in Ryze AI, disconnect with the trash icon and connect again. PostHog says the key value is shown once, a user can hold up to 10 personal API keys, and scopes can be changed later.
What Muse can do in PostHog
Muse gets 3 PostHog tools from the Ryze AI connector: 1 that reads, 1 that writes and 1 that deletes. Each full name starts with posthog__, the provider prefix Ryze AI uses for PostHog.
| 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. |
Meta says Muse does not take many important actions without approval by default, and that you change the approval behavior in Settings. Its newsroom adds that nothing publishes, sends or spends without your approval. Check that setting before you hand Muse the write and delete tools, because posthog__delete removes an object for good. The wording of Meta's setting was not tried for this guide. The firmest control is the key itself: scopes limited to read keep Muse read-only.
No PostHog tool was called for this guide, so there is no table of tested calls. The tool names and descriptions above come from the Ryze AI tool list in its facts file, which records that the PostHog tools were not seen live.
Limits to know
PostHog and Ryze AI set these limits on what Muse can do with a project. The PostHog figures come from the pages linked in the numbers table below.
| Limit | Detail |
|---|---|
| Query window | PostHog stops unbounded HogQL queries through Ryze AI, so a query needs a time window and a row limit of 1,000 at most. This bound is a Ryze AI rule from its facts file. |
| One project | One connection holds one PostHog project. |
| Write reach | Muse changes only what the key's write scopes allow. |
| Plan needed | The tools need an active Ryze AI plan or free trial. Without one, the connector can only list workspaces and connect platforms. |
| Cached answers | PostHog caches API queries by default, and a response says so with is_cached and last_refresh. |
| Muse connector limits | Meta does not review custom connectors or how they use data, and its pages describe no server URL field. How Muse treats its tool list after you connect more platforms in Ryze AI was not tested. |
Limits in numbers
| Limit | Number | Source |
|---|---|---|
| Query endpoint | Project level: 2,400 requests per hour, 240 per minute, 3 queries running at once, 10 seconds of max execution time | PostHog queries |
| Hourly read budget | Queries made with a personal API key draw from a per-project budget counted in bytes read. When it is used up the answer is 429 with api_queries_budget_exceeded. PostHog publishes no byte figure | PostHog queries |
| Analytics endpoints | 240 per minute and 1,200 per hour, per personal API key | PostHog API overview |
| Other create, read, update, delete endpoints | 480 per minute and 4,800 per hour, per personal API key | PostHog API overview |
| Rows per query | 100 by default, up to 50,000 with your own LIMIT. OFFSET returns HTTP 400 for personal API keys | PostHog queries |
| Rows per query through Ryze AI | 1,000 at most, with a time window | Ryze AI facts file |
| Personal API keys per user | Up to 10 | PostHog personal API keys |
| Dynamic cohorts | Updated once every 24 hours | PostHog cohorts |
| Free tier | The first 1,000,000 product analytics events each month are free. The free plan has 1 project and 1 year of data retention | PostHog pricing |
| Who the limits count against | Most count per personal API key, not per team. Requests made with OAuth or a logged-in session do not count against them | PostHog API overview |
Sources: PostHog API overview, PostHog HogQL queries, PostHog MCP FAQ, PostHog personal API keys, PostHog pricing, PostHog cohorts, Ryze AI PostHog guide. Checked November 14, 2026. Meta help: Muse connectors. Checked November 8, 2026.
First 3 prompts to run
1. Dashboard inventory
List the dashboards in my PostHog project by name, so I can pick one to ask about.
Tools used: posthog__read
What comes back: The dashboards in the connected project with their names. If PostHog answers with a 403 that names a missing scope, add that read scope to the key.
2. Traffic by campaign
Break down sessions for the last 30 days by UTM source with a HogQL query, limited to 1,000 rows.
Tools used: posthog__read
What comes back: One row for each UTM source with its session count, read from your own events. The time window and row limit keep the query inside what Ryze AI and PostHog accept.
3. Funnel read
Read my saved signup funnel insight and tell me how many people reach each step.
Tools used: posthog__read
What comes back: The steps of the saved funnel with the people at each step, computed from your project. Nothing in PostHog changes.
These answers come from your own project, so this page says what comes back and shows no sample figures.
10 jobs to hand to Muse
Ten jobs for Muse, each with its Ryze AI tool. No PostHog call was run for this guide; the jobs follow the Ryze AI tool list and PostHog's scope rules. Meta says Muse does not take many important actions without approval by default, which covers the jobs that change the project unless you change that setting.
| Job | Type this in Muse | Tool | Works on the default connection |
|---|---|---|---|
| Dashboard list | List the dashboards in my PostHog project with their names. | posthog__read | Conditional. Needs dashboard:read on the key, which the help center does not name. Not tested |
| Daily pageviews | Count pageviews per day for the last 7 days with a HogQL query, 1,000 rows at most. | posthog__read | Yes. Needs the Query scope |
| Traffic sources | Break down last month's sessions by UTM source with a HogQL query over sessions. | posthog__read | Yes. Needs the Query scope |
| Funnel report | Read my saved signup funnel insight and report how many people reach each step. | posthog__read | Yes. Needs the Insight and Query scopes |
| Flag audit | List my feature flags with their current rollout settings before a launch. | posthog__read | Conditional. Needs feature_flag:read on the key. Not tested |
| Cohort list | List the cohorts in the project and what defines each one. | posthog__read | Conditional. Needs cohort:read on the key. Not tested |
| Event check | List the event definitions so I can see which events exist before I build a report. | posthog__read | Conditional. Needs event_definition:read on the key. Not tested |
| Campaign insight | 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 confirm it. | posthog__delete | No. Needs cohort:write on the key, and the deletion cannot be undone |
Two limits sit behind these jobs. The Ryze AI facts name no session recordings, experiments, surveys or error tracking tools, so ask Muse for none of those. A PostHog project holds one connection per workspace.
5 ways to connect Muse to PostHog
Five ways exist on the pages checked for this guide, and only the first is documented end to end for Muse. Meta describes custom connectors as something you ask Muse to create. PostHog hosts its own server, two third-party connector pages name Muse, and reporting tools export PostHog data on a schedule. The Ryze AI connector is the main way: one address, a key kept in Ryze AI, nothing to build or host.
| Way | Runs where | Setup in Muse | What it reaches | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI at a single shared address | Ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, work through the guided setup and sign in to Ryze AI from the link. The Ryze AI page at ryze.ai/muse supplies a message to paste | 3 PostHog tools: read with HogQL, write and delete, for one project | Paid Ads at $89 per month with a 7-day trial. Connecting is free |
| PostHog MCP server (hosted by PostHog) | Hosted by PostHog at https://mcp.posthog.com/mcp (streamable HTTP) | PostHog's docs list Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed, and no Muse setup. Meta documents no field for a server URL. Untried with Muse. Sign-in is OAuth, or a personal API key with the MCP Server preset sent as a Bearer header | A wide set of PostHog areas: product analytics, web analytics, session replay, feature flags, experiments, error tracking, logs, surveys, SQL and more. PostHog's page counted 1,284 tools on November 14, 2026 | Free per PostHog. 480 requests per minute and 4,800 per hour per credential |
| Composio (hosted) | Hosted by Composio at https://connect.composio.dev/mcp | Composio's PostHog toolkit page lists Muse among the assistants it names. Authenticate in Composio, then connect PostHog with your own API key. The steps inside Muse were not checked | 686 tools and 11 triggers listed for the Posthog toolkit | Free plan $0 with a monthly tool call cap, Standard $18 per seat per month, per Composio's pricing page |
| AnythingMCP (cloud or self-hosted) | AnythingMCP Cloud in Frankfurt, or your own server with Docker | AnythingMCP's PostHog guide names Meta Muse among its assistants. You set a PostHog personal API key and host, then add your AnythingMCP server URL. The steps inside Muse were not checked | 28 MCP tools for PostHog, including HogQL and insight queries, dashboards, flags and cohorts. Its guide says it does not create or edit dashboards, cohorts or experiments, and 3 delete tools are off at install | Cloud: Starter 19 euros per month with a 7-day trial. The Community edition is free under AGPL-3.0 for up to 3 active users |
| Windsor.ai and Coupler.io (scheduled exports) | Hosted data services that pull PostHog data into their own store | Neither page checked names Muse among its AI destinations. Windsor.ai and Coupler.io connect PostHog as a data source with an API key, then hand the data to a listed assistant | Windsor.ai lists 101 PostHog fields. Coupler.io exports 7 entities: projects, cohorts, feature flags, persons, events, annotations and insights | Both have free plans with limits. Windsor.ai paid plans start at $19 per month billed annually, and Coupler.io Starter is $32 per month |
Options that do not fit Muse
- PostHog CLI and Wizard (posthog-cli, npx @posthog/wizard mcp add) install on your computer for terminals, coding agents and CI. Muse has no command line side in the pages reviewed.
- PostHog AI plugin (PostHog/ai-plugin) adds the PostHog server plus skills and slash commands to AI coding tools. It is a plugin for editors, not for a chat assistant.
- Zapier MCP lists 1 PostHog action, Capture Event, and no read of insights, dashboards, flags or cohorts, so it cannot answer analytics questions.
- viaSocket and Pipedream MCP list 12 and 10 PostHog actions. Pipedream names Create Query for HogQL, and neither page names Muse.
- Retired routes. The PostHog/mcp repository is archived and its README says the server moved into the PostHog monorepo. The npm package @posthog/agent-toolkit is deprecated in favor of the hosted MCP server. The npm package @posthog/mcp tracks tool usage in your own MCP server and does not connect to PostHog data.
Which one to pick
Ryze AI is the best way to connect Muse to PostHog for reading product analytics and running HogQL from a Muse chat, with one caveat: it reaches one PostHog project per connection, and Muse's own setup for it follows Meta's pages, which were not tried here. Use PostHog's hosted server if you want PostHog's full tool list and can get Muse to accept its address and sign-in, which is untried. Use Composio or AnythingMCP only if their Muse listings fit you better. Use the exports for scheduled reports rather than live questions.
Sources: PostHog MCP overview, PostHog MCP docs, PostHog MCP FAQ, PostHog connector in Claude, PostHog plugin in ChatGPT, PostHog CLI docs, PostHog ai-plugin on GitHub, Composio PostHog toolkit, Zapier PostHog MCP, Windsor.ai PostHog fields, Coupler.io PostHog, AnythingMCP guide, viaSocket PostHog MCP, Pipedream PostHog MCP, Ryze AI PostHog guide. Checked November 14, 2026. Meta help: Muse connectors, Meta newsroom: Muse for small business, Ryze AI Muse page. Checked November 8, 2026.
PostHog, Muse and MCP: dates that matter
| Date | What happened |
|---|---|
| May 14, 2025 | The PostHog/mcp repository was created as the official PostHog MCP server. It is now archived, and its README says the server moved into the PostHog monorepo. |
| February 27, 2026 | PostHog's changelog announced a PostHog connector for Claude, and the same day added cohort management through PostHog MCP. |
| May 4, 2026 | PostHog added explicit MCP mode selection with the x-posthog-mcp-mode header or the mode query parameter. |
| September 2026 | Meta launched Muse for small business, available in the US and Canada, with custom connectors. |
| September 24, 2026 | The Ryze AI Muse page was last updated, per the page. |
| October 1, 2026 | PostHog's changelog announced longer-lived MCP connections for clients with non-rotating refresh tokens, which no longer ask for a new authorization after roughly 67 days. |
| October 22, 2026 | PostHog's changelog announced 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. |
| November 5, 2026 | New events retention periods began applying to organizations that start a paid plan on or after this date. |
| November 14, 2026 | posthog.com/mcp, built that day, counted 1,284 tools in 78 categories. No launch date for the hosted server at mcp.posthog.com is published on the pages checked. |
Sources: PostHog changelog 2026, PostHog personal API keys, PostHog/mcp repository, npm: @posthog/agent-toolkit, PostHog events retention, PostHog MCP overview. Checked November 14, 2026. Meta newsroom, September 2026, Ryze AI Muse page. Checked November 8, 2026.
How this guide was tested
This guide rests on two kinds of checks: requests to the Ryze AI connector on November 20, 2026, and a read of PostHog's public pages on November 14, 2026. No result comes from a PostHog project.
| What was run | What came back |
|---|---|
| The connector address without a sign-in, November 20 | A POST to https://connector.get-ryze.ai/mcp returned HTTP 401 with error invalid_token and a WWW-Authenticate header that points at the sign-in details, which is how an OAuth-protected server normally answers. |
| The sign-in discovery file, November 20 | The authorization server metadata loaded from the connector host. It lists the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE and the scopes mcp:read and mcp:write. |
| PostHog's pages, November 14 | The API overview, scopes, personal API keys, queries, MCP docs and FAQ, pricing and changelog were read as page text, and the third-party connector pages named in Sources were opened. |
| Muse listings on third-party pages, November 14 | Composio's PostHog toolkit page and AnythingMCP's PostHog guide name Muse among their assistants. Coupler.io and Windsor.ai do not. |
Not run for this guide: any call to PostHog. No PostHog test project was connected, so none of the 3 posthog__ tools ran, and their names come from the Ryze AI facts file. No step inside Muse was run either. No Muse account was used, so the chat request, the guided setup, the sign-in link and Meta's approval setting follow Meta's pages and the Ryze AI Muse page as read on November 8, 2026. For that reason this page has no table of tested calls and no error messages seen in a test.
Errors and fixes
Error codes from PostHog's documentation
These errors come from PostHog's documentation, not from a test. How the Ryze AI tools relay them was not checked.
| Code and message | What it means | What to do |
|---|---|---|
| 401 authentication_error, invalid_personal_api_key: Invalid Personal API key. | The personal API key is invalid. | Create a new key in Settings, Personal API keys, then disconnect and connect PostHog again in Ryze AI. |
| 403 naming a missing scope | The request needs a scope the key does not have. | Add the named scope to the key in PostHog. Scopes can be changed later. |
| 429 api_queries_budget_exceeded, with a Retry-After header | The project's hourly read budget for personal API key queries is used up. Cached results still work. | Wait for the Retry-After time, then ask for a narrower window or fewer rows. |
| 400 on OFFSET | OFFSET paging on the query endpoint is rejected for personal API keys. | Ask for the next rows with a timestamp filter instead of an offset. |
| 429 from PostHog's own MCP server, with a Retry-After header | A credential passed 480 requests per minute or 4,800 per hour on mcp.posthog.com. This applies to PostHog's server, not to the Ryze AI connector. | Only relevant if you use PostHog's hosted server. Wait, then retry. |
Sources: PostHog API overview, PostHog API scopes, PostHog HogQL queries, PostHog MCP FAQ. Checked November 14, 2026.
Other problems
- Muse does not offer to create the connector
- Meta limits Muse to the US and Canada. Check your region, then ask plainly: create a custom connector for https://connector.get-ryze.ai/mcp.
- No field for the server URL
- Meta's pages describe none. You ask Muse in a chat to create the connector, and the Ryze AI Muse page has a message to paste.
- The sign-in link does not open the Ryze AI page
- Tell Muse to continue the Ryze AI connector setup and send a fresh link. Meta's pages do not say how long a link lasts.
- Muse asks me to approve every action
- Meta says Muse by default holds back many important actions until you approve, and that Settings changes this.
- Ryze AI rejects the key or host
- Check that you pasted the whole phx_ key and that the host matches your region: https://us.posthog.com, https://eu.posthog.com or your self-hosted address.
- The PostHog tools are missing
- If the connector was created before PostHog was connected, remove it under Settings, then Connectors in Muse, create it again and open a new chat. Whether Muse refreshes tool lists by itself was not tested.
- A change is refused
- The key probably has read scopes only, and PostHog rejects any change. Create a key with the write scope for that object, or keep it read-only on purpose.
- The one-time connection link is refused
- Ryze AI refuses the link while PostHog is already connected in the workspace. Switch project or key in the Ryze AI app instead.
- Muse reports that a subscription is required
- The tools need an active Ryze AI plan or free trial. Start the trial or fix the card in Ryze AI billing, then retry.
Terms on this page
- MCP
- The Model Context Protocol. The Ryze AI Muse page says the connector speaks it over HTTP with OAuth, a detail Meta's pages never mention.
- Custom connector
- Meta's term for a link to a service Muse lacks built in, created by asking Muse in a chat.
- Personal API key
- A PostHog key that starts with phx_ and authenticates the private API endpoints as your own user. You choose its scopes, and you can create up to 10.
- Scope
- PostHog's unit of access to one part of the product, such as feature flags or insights. Each scope has a read level and a write level.
- HogQL
- PostHog's SQL, a wrapper around ClickHouse SQL, used to query events, persons and sessions.
- Insight
- A saved analysis in PostHog and the main building block of product analytics. Types include trends, funnels and retention.
- Cohort
- A list of users who have something in common. Static cohorts do not change, and dynamic cohorts update once every 24 hours.
- Host
- The PostHog address your account lives on: US Cloud, EU Cloud or your own domain when self-hosted.
Sources: Meta help: Muse connectors, Meta newsroom: Muse for small business. Checked November 8, 2026. PostHog personal API keys, PostHog API scopes, PostHog SQL, PostHog insights, PostHog cohorts, PostHog feature flags. Checked November 14, 2026.
Frequently asked questions
How do I connect Muse to PostHog?
Create a personal API key in PostHog under Settings, Personal API keys, and paste it with your host into the PostHog card in Ryze AI. Then in a Muse chat, ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp, follow the guided setup and sign in to Ryze AI from the link Muse sends.
Is there a PostHog connector for Muse?
Yes: ask Muse to create a custom connector for the Ryze AI address, https://connector.get-ryze.ai/mcp, and Muse gets 3 PostHog tools. Composio and AnythingMCP also list Muse on their PostHog pages, and PostHog's own docs list no Muse setup.
Is there a Muse PostHog MCP server?
PostHog hosts an MCP server at https://mcp.posthog.com/mcp, and Ryze AI hosts a separate one at https://connector.get-ryze.ai/mcp. PostHog's docs give setup for Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed, not Muse, and using PostHog's address in Muse is untried.
Where is Muse available, and which plan do I need?
Meta says Muse is available in the US and Canada. Its help and newsroom pages reviewed name no plan for custom connectors, so no plan requirement is stated here.
Is there a field for the server URL in Muse?
Meta's pages describe none. Custom connectors are created by asking Muse in a chat, and Muse starts a guided setup. The Ryze AI page at ryze.ai/muse has a ready-made message to paste.
Which PostHog key and scopes does Muse need?
A personal API key that starts with phx_, with read access to the wanted projects including the Query and Insight scopes. Add write scopes only for objects Muse should change. PostHog says a request without the needed scope fails with a 403 that names it.
Can Muse run HogQL queries on PostHog?
Yes. posthog__read runs HogQL analytics queries over events, persons and sessions. Through Ryze AI a query needs a time window and a row limit of 1,000 at most.
Can Muse change my PostHog project?
Only if the key has write scopes. posthog__write creates or updates insights, dashboards, feature flags and cohorts, and posthog__delete removes them. With read scopes only, PostHog rejects any change.
Does Muse ask before it changes PostHog?
Meta says by default Muse does not take many important actions without approval, and its newsroom says nothing publishes, sends or spends without your approval. You change the approval behavior in Settings. This was not tried for this guide, so check the setting, or keep the key read-only.
Does Meta review custom connectors?
No. Meta says it does not review custom connectors or how they use data, and that Muse stores the credentials in its Secure Credentials Store. Review what the PostHog key can do before you connect it.
Can I connect more than one PostHog project?
Not in one workspace. One connection holds one project. To switch, click View on the PostHog card, disconnect with the trash icon and connect again. Another project can live in another workspace.
Does it work with PostHog EU Cloud or self-hosted?
Yes. When you connect, enter https://eu.posthog.com for EU Cloud, https://us.posthog.com for US Cloud, or your own address for a self-hosted instance.
How do I remove the connector from Muse?
Open Settings, then Connectors in Muse to manage or disconnect it. To cut access on the PostHog side, delete the personal API key in PostHog.
How much does it cost to connect Muse to PostHog?
Connecting is free, but the tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, and annual billing takes 30% off the first year. PostHog's own charges are separate, and its free tier covers the first 1,000,000 product analytics events each month.
Has Ryze AI been tested with PostHog in Muse?
Not inside Muse and not against a PostHog project. The connector address was checked on November 20, 2026 and PostHog's public pages on November 14, 2026. The Muse steps follow Meta's pages and the Ryze AI Muse page. Ryze AI has no help center page for Muse, so report any difference to Ryze AI support.