By Ira Bodnar, Ryze AI · Updated · Connector address tested November 17, 2026
Quick answer
The main way to connect Le Chat to PostHog is the Ryze AI connector. Save a PostHog personal API key and your host in Ryze AI, pick the project, then, in Mistral Vibe (the name Le Chat has carried since May 2026), open Connectors, click + Add Connector, choose the Custom MCP Connector tab, enter a name such as RyzeAI with the server URL https://connector.get-ryze.ai/mcp, click Connect and finish the Ryze AI sign-in.
- In PostHog create a personal API key with read access to your project, including the Query and Insight scopes
- In Ryze AI open Integrations, click Connect on the PostHog card, paste the key, set the host and pick the project
- In Mistral Vibe open Connectors, + Add Connector, Custom MCP Connector, then enter the name and URL
- Click Connect, finish the Ryze AI sign-in, choose workspaces and click Allow connection
Le Chat to PostHog at a glance
| Fact | Detail |
|---|---|
| Main way | The Ryze AI connector, added to Mistral Vibe as a Custom MCP Connector |
| Address to enter | https://connector.get-ryze.ai/mcp |
| Sign-in | A PostHog personal API key and host saved once in Ryze AI, then a Ryze AI sign-in from Mistral, which detects OAuth 2.1 with dynamic client registration. No client ID or secret to type |
| PostHog tools | 3: one read, one write, one delete |
| Changes to PostHog | Only if the key has write scopes. A key with read scopes keeps the agent read-only, because PostHog rejects any change. Mistral Vibe asks before a call that creates, modifies, sends, posts or deletes |
| Other data in the same chat | Ads and SEO data from the other platforms in the Ryze AI agent, next to one PostHog project |
| Mistral requirement | An administrator adds the connector. On Free, Pro and Student the account owner is the administrator. No minimum plan is named |
| Ryze AI price | Paid Ads, $89 per month with a 7-day free trial. Adding the connector is free |
| PostHog's own option | A hosted MCP server at https://mcp.posthog.com/mcp, free to connect. PostHog's pages do not name Le Chat, and it was not tried in Vibe Work |
| Last tested | The connector address on November 17, 2026. No PostHog call was run and nothing was run inside Mistral Vibe |
Before you start
- Administrator rights in Mistral. Mistral's docs call adding a custom MCP connector an administrator-only action, and on Free, Pro and Student plans the account owner is the administrator by default. The docs name no minimum plan. On a team or organization account, ask an administrator to add it.
- A PostHog personal API key. It starts with phx_. Ryze AI asks for read access to the projects you want, including the Query and Insight scopes, and for the host: https://us.posthog.com for US Cloud, https://eu.posthog.com for EU Cloud, or your own address when self-hosted. Add write scopes only if the agent should change things.
- A Ryze AI workspace on a plan or free trial. Paid Ads costs $89 per month with a 7-day free trial, and annual billing takes 30% off the first year. Adding the connector is free; the PostHog tools run only with an active plan or trial.
- A server reachable over HTTPS. Mistral requires a valid TLS certificate. The Ryze AI address meets that, so enter it exactly as written.
How to connect Le Chat to PostHog
Setup has two parts. PostHog is linked inside Ryze AI first, and then Mistral Vibe gets the address of the Ryze AI connector. The Mistral half follows Mistral's MCP connectors docs. Ryze AI has no help center page for Mistral, and nobody ran the sign-in inside Mistral Vibe while this guide was written, so check the errors section below if a screen looks different. If you prefer, ask the Ryze AI agent in Claude or ChatGPT to connect PostHog: it sends a one-time link, valid once and for 24 hours, to a page where you paste the key and the host.
Create a personal API key in PostHog
In PostHog go to Settings, then Personal API keys, and click Create key. Give it read access to the projects you want, including the Query and Insight scopes. Add write scopes only for objects the agent may change. Copy the phx_ key, because PostHog shows it once.
Save the key in Ryze AI
In the Ryze AI app open Integrations, click Connect on the PostHog card, paste the key, enter the host (US Cloud, EU Cloud or your self-hosted address) and click Continue. Pick the Project and click Save.
Open Connectors in Mistral Vibe
Go to chat.mistral.ai (the address stayed the same when Le Chat became Mistral Vibe), open the Connectors page from the sidebar and click + Add Connector. Switch to the Custom MCP Connector tab.
Enter the connector name and URL
Connector name: a unique identifier with no spaces or special characters, for example RyzeAI. Server URL: https://connector.get-ryze.ai/mcp. The description is optional.
Click Connect
Mistral detects the authentication method by itself. Ryze AI uses OAuth 2.1 with dynamic client registration, so no client ID or secret is entered.
Finish the Ryze AI sign-in
Complete the Ryze AI sign-in when Mistral prompts, choose the workspace that holds your PostHog connection and click Allow connection. Start a new chat and ask a PostHog question. If the connector was added before PostHog was connected, remove it, add it again and open a new chat.
There is no Ryze AI help center page for Mistral Vibe. The Ryze AI PostHog guide covers the PostHog key and host on the Ryze AI side.
Sources: Mistral docs: MCP connectors, Mistral docs: Connectors, Mistral help: Le Chat is now Vibe, PostHog personal API keys, Ryze AI PostHog guide. Checked November 15, 2026.
Approvals and Always allow
Mistral lets each user decide how much a function may do without asking. To pre-authorize only the reads you trust:
- Open Connectors, then the My Connectors tab.
- Open the Ryze AI card and go to its Functions tab.
- Switch Always allow on for posthog__read if you want queries to run without a prompt each time.
- Leave Always allow off for posthog__write and posthog__delete, so Mistral asks before each one.
- Use Refresh tools on the same tab to reload the function list after Ryze AI changes it.
Mistral's Safety and approvals page says Work pauses before anything that creates, modifies, sends, posts or deletes, and gives three answers: Continue for that one action, Always allow for that function until the session ends, or Decline. The toggles on the Functions tab belong to each user, so your choices do not change a teammate's settings. Mistral advises keeping write functions on manual approval until you trust the connector. The surest way to keep PostHog untouched is a personal API key with read scopes only, because PostHog then rejects any change.
Sources: Mistral docs: MCP connectors, Mistral docs: Safety and approvals. Checked November 15, 2026.
Vibe Work and Vibe Code
Vibe Work and the old Le Chat address
Mistral's changelog and launch post date the switch from Le Chat to Vibe to May 28, 2026, with the same chat.mistral.ai address and the same login. Since September 22, 2026 the old Chat tab and Work run as one experience, and the Connectors page sits in Work. Mistral's old docs link for MCP connectors redirects to the Vibe docs, so a tutorial that still says Le Chat describes this same screen.
Vibe Code (CLI and VS Code extension)
Vibe Code, the coding side of Vibe, keeps MCP servers in ~/.vibe/config.toml or in a project's .vibe/config.toml and adds them with vibe mcp add. Mistral's docs say a remote server added by URL opens the browser to sign in, and that Vibe Code can also start a local server from a command, which Work cannot. Ryze AI has not reviewed the Vibe Code setup, so this guide gives steps for Vibe Work only.
Vibe Work and MCP: the facts in one table
| Topic | What Mistral pages say |
|---|---|
| Product name | Vibe. Work, on the web and in the iOS and Android apps, is the old Le Chat. Mistral does not say whether a custom connector can be added or used from the apps |
| Where a server is added | The Connectors page from the sidebar, + Add Connector, Custom MCP Connector tab |
| Plan | The connector docs name no minimum plan. Mistral's pricing page shows a check mark for the beta Custom MCP connectors feature under Free, Pro, Team and Enterprise |
| Who can add one | An administrator, which on Free, Pro and Student is the account owner by default |
| Transport | A remote address over HTTPS with a valid TLS certificate. Mistral shows no field for a local command |
| Sign-in | Detected from the URL: none, a Bearer token or Basic Auth in the Authorization header, or OAuth 2.1 with dynamic client registration |
| Approval | A prompt before actions that create, modify, send, post or delete: Continue, Always allow for the session, or Decline |
| Picking the connector | Work calls a connected connector when it fits the request. The + icon or / in the chat box, then Tools, picks one for a task |
| Not supported yet | Dynamic tool discovery, resources and automatic prompt templates |
| Where it is managed | Users: Connectors, My Connectors tab. Admins: Admin Panel, Administration, Connectors, set to Allowed, Restricted or Blocked per workspace |
Sources: Mistral docs: Vibe, Mistral docs: MCP connectors, Mistral docs: Safety and approvals, Mistral docs: Admin Panel connectors, Mistral docs: Vibe Code MCP servers, Mistral pricing. Checked November 15, 2026.
PostHog access and API key scopes
Three gates sit between Mistral Vibe and your analytics. Mistral decides who may add the connector and which calls ask first, Ryze AI decides which PostHog project is reachable, and the scopes on your personal API key set what PostHog allows.
- Which project
- One PostHog project per connection. You pick it after saving the key, and the host decides which PostHog region is used. To switch projects, click View on the PostHog card in Ryze AI, disconnect and connect again. Another project can live in another Ryze AI workspace.
- Which user the key acts as
- PostHog says a personal API key gives the same access as being logged in to PostHog as the person who made it, within the scopes and projects set on the key. A person can hold up to 10 personal API keys.
- What Mistral lets through
- Work asks before a call that creates, modifies, sends, posts or deletes. In an organization, an admin can set the Connectors setting to Allowed, Restricted or Blocked per workspace, so an admin may have switched custom connectors off for yours.
Ryze AI asks for a personal API key with read access to the projects you want, including the Query and Insight scopes, and says to add write scopes only if the agent should make changes. PostHog gives every scope a read level and a write level, and write access includes read access. A call that needs a scope the key lacks fails with a 403 that names the missing scope.
Scopes on the PostHog personal API key
The table lists the PostHog scopes that match what the three Ryze AI tools work on. The Ryze AI facts name only the Query and Insight scopes. Whether listing dashboards, flags, cohorts, persons or event definitions also needs its own scope on the key is not stated there, so those rows are marked as unconfirmed. If a read comes back with a 403, add the scope it names.
| Scope | What PostHog says it covers | With Ryze AI |
|---|---|---|
| query:read | Running SQL and insight queries on the project's data, plus event, session and web vitals lookups. Read level only | Named in the Ryze AI facts. Needed for HogQL queries |
| insight:read, insight:write | Insights, including their queries, results and explanations | Named in the Ryze AI facts. Write only if the agent should create or edit insights |
| dashboard:read, dashboard:write | Dashboards, including their tiles, text cards and layout, and running the insights on them | Not named in the Ryze AI facts. Write only for dashboard changes |
| feature_flag:read, feature_flag:write | Feature flags, including release conditions, variants, payloads and rollout history | Not named in the Ryze AI facts. Write only for flag changes |
| cohort:read, cohort:write | Cohorts, including their filters, static member lists and calculation history | Not named in the Ryze AI facts. Write also covers deleting a cohort |
| person:read, person:write | Persons and their properties, including updating, splitting and deleting persons and their data | Not named in the Ryze AI facts. Read if you want person lookups |
| event_definition:read | Event definitions, schemas and property groups | Not named in the Ryze AI facts. Read if you want to list events |
Not on the table: session recordings, experiments, surveys and error tracking. The Ryze AI facts name insights, dashboards, feature flags, cohorts, persons, event definitions, projects and HogQL queries, so this guide claims nothing more. PostHog's own MCP server covers those other areas; see the comparison below.
What a PostHog key can reach
A key can apply to the whole organization, to specific projects or to all projects, and its scopes can be changed later. PostHog shows the key value once, at creation. Organization admins and owners can see every member's key that reaches the organization, with its scopes and last use. Keys that appear in public GitHub repositories are found by secret scanning and rolled automatically.
Sources: PostHog API scopes, PostHog personal API keys, PostHog API overview, Ryze AI PostHog guide. Checked November 14, 2026.
Removing access
You can cut access in three places. Click View on the PostHog card in Ryze AI and disconnect with the trash icon, delete the personal API key in PostHog under Settings, Personal API keys, or open Connectors, My Connectors in Mistral Vibe and remove the Ryze AI connector.
What Le Chat can do in PostHog
The Ryze AI connector gives Mistral Vibe 3 PostHog tools: 1 that reads, 1 that writes and 1 that deletes. Mistral calls an action of a connector a function; this page says tool. Ryze AI has not listed these names from a live connection, so they come from the Ryze AI facts.
| Tool | Type | What it does |
|---|---|---|
| posthog__read | Read | Reads data for the connected project: projects, insights, dashboards, feature flags, cohorts, persons and event definitions. Also 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. |
Mistral sorts connector functions into read and write. Work asks before a call that creates, modifies, sends, posts or deletes, and you can switch on Always allow per function under Connectors, My Connectors, the Ryze AI card, Functions tab. Mistral suggests keeping write functions on manual approval, so leave Always allow off for the write and delete tools. Mistral's pages do not say whether a custom connector's read functions ask by default. The Ryze AI chat is a separate place: its Tool approvals picker starts on Skip all approvals, and scheduled tasks run without an approval step. A PostHog object that was deleted cannot be brought back through Ryze AI.
Limits in numbers
HogQL through Ryze AI needs a time window and a row limit of 1,000 at most, because PostHog stops unbounded queries. That rule comes from Ryze AI, not from a PostHog page. The PostHog figures below are the vendor's, and most count per personal API key, not per project. Mistral's connector docs print no cap on the number of tools or calls.
| Limit | Number |
|---|---|
| Analytics endpoints | 240 per minute and 1200 per hour per personal API key. This covers calculating insights and retrieving persons |
| Query endpoint | 2400 per hour on the API overview. The queries page puts it at project level: 240 per minute, 3 queries running at once, 10 seconds of maximum execution time. A queued query may wait up to 30 seconds |
| Other create, read, update and delete endpoints | 480 per minute and 4800 per hour per personal API key |
| Hourly read budget | Queries made with a personal API key draw from a read budget per project, counted in bytes. When it is used up the answer is 429 with the code api_queries_budget_exceeded. Cached results still work. PostHog publishes no byte figure |
| Rows per query | 100 by default. With your own LIMIT, up to 50k rows. OFFSET returns HTTP 400 for personal API keys, so use keyset pagination on timestamp |
| Query cache | API queries are cached by default, and a response says so with is_cached and last_refresh |
| Who the limits count against | Most count per personal API key. Requests made with OAuth or a logged-in session do not count against the key limits |
| Personal API keys per user | Up to 10 |
| Dynamic cohorts | Updated once every 24 hours |
| PostHog's own MCP server | 480 requests per minute and 4,800 per hour per credential. This applies to mcp.posthog.com, not to the Ryze AI connector |
| Connector name in Mistral | Unique, with no spaces or special characters |
Sources: PostHog API overview, PostHog queries, PostHog MCP FAQ, PostHog personal API keys, PostHog cohorts, Mistral docs: MCP connectors. Checked November 14, 2026.
First 3 prompts to run
Each prompt below says what it asks for and which tool it uses. The answers depend on your own project, so no sample figures appear here.
1. Pageviews per day
Use the RyzeAI connector to run a HogQL query that counts pageviews per day for the last 7 days, with a row limit of 100.
Tools used: posthog__read
What comes back: A table of days and counts from a HogQL query over events. The time window and row limit in the prompt keep it inside the bounds Ryze AI sets.
2. Traffic by UTM source
With RyzeAI, break down last month's sessions by UTM source with a HogQL query over sessions, 50 rows at most, and tell me which sources sent the most.
Tools used: posthog__read
What comes back: Sessions grouped by UTM source for the month, ordered by size. It shows which campaigns sent visitors, and says nothing about what they spent.
3. Read a saved funnel
Ask RyzeAI to read my saved signup funnel insight and report how many people reach each step.
Tools used: posthog__read
What comes back: The step counts of a saved funnel insight, read from the project. Nothing is changed.
Start with prompts that only read. When Mistral asks permission for a write, check the action it describes before you click Continue. A write needs a key with write scopes, so on a read-only key PostHog rejects the change.
10 jobs to hand to Le Chat
Ten jobs to give Le Chat once the connector is in, each with its Ryze AI tool. Name the RyzeAI connector in the request, or pick it from the Tools menu in the chat box. No PostHog call was run for this guide, so every row rests on the Ryze AI facts and on PostHog's documentation.
| Job | Ask Le Chat | Tool | Works on the default connection |
|---|---|---|---|
| Daily pageviews | Count pageviews per day for the last 7 days with a HogQL query, 100 rows at most. | posthog__read | Yes, with the Query scope |
| Campaign traffic | Break down last month's sessions by UTM source to see which campaigns sent traffic. | posthog__read | Yes, with the Query scope |
| Funnel check | Read my saved signup funnel insight and report how many people reach each step. | posthog__read | Yes, with the Insight and Query scopes |
| Dashboard list | List the dashboards in the project with their names. | posthog__read | Depends on the key. Needs dashboard:read if PostHog asks for it |
| Flag review | List the feature flags with their current rollout settings before a launch. | posthog__read | Depends on the key. Needs feature_flag:read if PostHog asks for it |
| Cohort list | List the cohorts in the project and what defines each one. | posthog__read | Depends on the key. Needs cohort:read if PostHog asks for it |
| Event inventory | List the event definitions to check which events exist before building a report. | posthog__read | Depends on the key. Needs event_definition:read if PostHog asks for it |
| 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 |
| Remove a test cohort | Delete the old test cohort I name. It cannot be undone. | posthog__delete | No. Needs a key with cohort:write |
5 ways to connect Le Chat to PostHog
A custom connector in Vibe Work has to point at a remote MCP server over HTTPS, and Work cannot start a local command. Five ways into PostHog fit that shape. The Ryze AI connector is the main way: one key saved in Ryze AI, one address in Mistral and 3 tools for queries and changes. None of the other four vendors names Le Chat or Mistral on the pages read on November 14, 2026, and none was tried in Vibe Work.
| Way | Runs where | Setup in Mistral Vibe | What it reaches in PostHog | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user. The same address works in Claude, ChatGPT and other MCP clients | An administrator adds a Custom MCP Connector named, for example, RyzeAI with https://connector.get-ryze.ai/mcp, clicks Connect and signs in. The PostHog key and host are saved once in Ryze AI | 3 tools: reads of insights, dashboards, flags, cohorts, persons and event definitions, HogQL queries, writes, and a separate delete tool. One project per connection | Paid Ads $89 per month, 7-day free trial. Adding the connector is free |
| PostHog's hosted MCP server | Hosted by PostHog at https://mcp.posthog.com/mcp (streamable HTTP) | PostHog says to add the URL in the client and sign in to PostHog with OAuth, or send a personal API key made with the MCP Server preset as an Authorization: Bearer header. PostHog documents Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed, and does not mention Le Chat. Mistral's page does not say where a Bearer token is typed | 1284 tools in 78 categories on posthog.com/mcp.md, including session replay, experiments, error tracking and surveys. A read-only mode and a feature filter are set with URL parameters | Free to connect and to call tools. PostHog says some tools use LLMs inside and may be billed as PostHog AI spend |
| Composio | Hosted | A remote MCP entry at https://connect.composio.dev/mcp, then an authorization in the browser. PostHog itself is connected with your own API key. Le Chat is not on Composio's assistant list | 686 tools and 11 triggers listed for its PostHog toolkit | Free: $0, with app tool calls stopping at 10,000 a month. Standard: $18 per seat per month |
| Zapier MCP | Hosted | Add Zapier as a connector and sign in. Zapier turns on actions for apps already linked to your Zapier account. Perplexity and Le Chat are not on the client lists read | 1 PostHog action, Capture Event. No read of insights, dashboards, flags or cohorts is listed | Each successful tool call uses two tasks from your Zapier plan |
| Pipedream MCP | Hosted at https://mcp.pipedream.net/v2 | Connect PostHog with an API key in Pipedream, then add the Pipedream server. The page names no Mistral steps | 10 actions: list and get insights, create and update insights, create a HogQL query, get persons, cohorts and surveys, and capture an event | No price on the page |
Other PostHog options left out of the table
- PostHog plugin in ChatGPT and the PostHog connector in Claude's directory. Both sit inside those assistants and run PostHog's own hosted server. Neither is an option inside Mistral Vibe.
- PostHog AI plugin, CLI and Wizard. They install on your computer for coding agents such as Claude Code, Cursor and Codex. Vibe Work takes only a remote HTTPS address, so they do not fit this chat.
- Windsor.ai and Coupler.io. Both pull PostHog data through their own sync and name other AI tools. The pages read do not describe a route into Mistral Vibe.
- Mistral's connector directory. Vibe Work also offers Featured Connectors and an MCP Connectors directory. This guide did not check whether either holds a PostHog connector.
Which one to pick
Ryze AI is the best way to connect Le Chat to PostHog for queries on one project with change control through a read-only key, with one caveat: it has 3 tools and no session replay, experiment, survey or error tracking coverage. PostHog's own server covers far more of PostHog and is free to connect, but PostHog does not name Le Chat, its sign-in with Mistral was not tried and it gives you 1284 tools to sort through. Composio, Zapier and Pipedream make sense when your team already uses one of them for other apps, and Zapier's single PostHog action cannot read data.
Sources: PostHog MCP server docs, PostHog MCP FAQ, PostHog MCP overview, Composio PostHog toolkit, Composio pricing, Zapier PostHog MCP, Zapier MCP quickstart, Pipedream PostHog MCP, Windsor.ai PostHog data fields, Coupler.io PostHog, Mistral docs: MCP connectors, Ryze AI PostHog guide. Checked November 14 and 15, 2026.
Le Chat, PostHog and MCP: dates that matter
| Date | What happened |
|---|---|
| September 2, 2025 | Le Chat gained custom MCP connectors and a directory of more than 20 connectors (beta), open to every user, Free plan included. |
| February 27, 2026 | PostHog's changelog announced a PostHog connector for Claude. The Claude directory listing shows Added February 2026. |
| May 4, 2026 | PostHog's MCP server gained explicit mode selection with the x-posthog-mcp-mode header or the mode query parameter, with the values tools and cli. |
| May 28, 2026 | Le Chat became Vibe at chat.mistral.ai, and Mistral's docs moved from /le-chat to /vibe. |
| June 24, 2026 | Mistral added per-workspace and per-tool connector controls for admins, connectors that hold several logins, and the Connectors Debugger. |
| September 22, 2026 | Chat and Work merged into one Vibe experience. Enterprise organizations move from October 1, 2026, within about six months. |
| October 1, 2026 | PostHog's changelog said MCP 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 described a simpler MCP install, with a separate flow for browser and account based clients such as ChatGPT and Claude. |
Sources: PostHog changelog 2026, Mistral changelog, Mistral news, September 2, 2025, Mistral news, May 28, 2026, Mistral news, June 24, 2026. Checked November 14 and 15, 2026.
How this guide was tested
Two things stand behind this guide: requests to the live Ryze AI connector address on November 17, 2026, and the vendors' own pages as read on November 14 (PostHog), November 15 (Mistral) and again on November 17 for the PostHog MCP FAQ and the Mistral connector docs. No PostHog account was connected, so no PostHog data was read or changed.
| What was run | What came back |
|---|---|
| The connector address, without signing in (November 17, 2026) | A POST to https://connector.get-ryze.ai/mcp came back as HTTP 401 with a WWW-Authenticate header of type Bearer that points to the protected resource metadata. Mistral's docs say an OAuth server should answer an unauthenticated request this way. |
| The sign-in details (November 17, 2026) | Both discovery files on the connector's host loaded. They name the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and two scopes: mcp:read and mcp:write. |
| PostHog documentation (November 14, 2026) | Scopes, personal API key rules, rate limits and query limits were read on PostHog's docs and copied into the tables above. |
| Mistral documentation (November 15 and 17, 2026) | The add steps, the administrator rule, the sign-in methods and the unsupported features were read on Mistral's docs. They matched on both days. |
Not run: any step inside Mistral Vibe. No Mistral account was used, so the Connectors form, the sign-in prompt, the Functions tab and the approval prompt follow Mistral's documentation. No PostHog call was run through the connector, so the three tool names come from the Ryze AI facts and not from a live tool list, and no read, write or delete was tried. For the same reason this guide shows no tested reads and no error messages seen in a test. The errors below are the ones PostHog and Mistral document.
Le Chat and PostHog errors and fixes
Messages the vendors document
None of these appeared in a test. They are the messages and codes that PostHog and Mistral document, with what each means and what to ask or do next.
| Message | What it means | What to do |
|---|---|---|
| Invalid Personal API key. | PostHog answers 401 with the code invalid_personal_api_key. The key saved in Ryze AI is wrong, deleted or mistyped. | Create a new key in PostHog, disconnect PostHog in Ryze AI and connect it again with the new key. |
| 403 that names the missing scope | The request needs a scope the key does not have, for example dashboard:read or feature_flag:read. | Add the scope the message names to the key in PostHog, then ask again. |
| api_queries_budget_exceeded | PostHog answers 429 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 time in Retry-After, or ask for a narrower time window and fewer rows. |
| HTTP 400 on OFFSET | PostHog rejects OFFSET pagination on the query endpoint for personal API keys. | Ask Le Chat to page with a timestamp filter instead of OFFSET. |
| MCP connection requires additional information or is invalid | Mistral prints this when its setup check fails. | Confirm the address ends in /mcp exactly as given, then click Connect again. |
Other problems
- Add Connector is missing or refused
- Mistral says adding a custom MCP connector is administrator-only. On Free, Pro and Student plans the account owner is the administrator. On a shared account, ask an administrator to add it. An organization admin may also have switched MCP Connectors off for your workspace.
- The connector name is rejected
- Mistral wants a unique name with no spaces or special characters. Use RyzeAI.
- The PostHog tools do not load
- Open a fresh chat, then click Refresh tools on the Functions tab of the Ryze AI card. If they are still missing, check that the PostHog card in Ryze AI reads Connected, then remove the connector and add it back. Mistral lists dynamic tool discovery as unsupported for custom connectors; how that affects a platform connected in Ryze AI later was not verified.
- The sign-in does not complete
- Finish the Ryze AI sign-in, choose workspaces and click Allow connection. If the window closed early, click Connect on the connector card again.
- The key is accepted but a query fails
- HogQL needs a time window and a row limit of 1,000 at most. Add both to the request, for example the last 7 days and 100 rows.
- A change is refused
- The key may have read scopes only. PostHog rejects any change from such a key, so add the write scope for that object, such as insight:write, and ask again.
- Data comes from the wrong region
- The host decides the region. Use https://us.posthog.com for US Cloud, https://eu.posthog.com for EU Cloud or your own address when self-hosted, and save it again on the PostHog card.
- I need a different project
- One PostHog project is saved per connection. Click View on the card, disconnect with the trash icon and connect again, or use another Ryze AI workspace for the second project.
- Ryze AI refuses the one-time link
- The one-time link is refused while PostHog is already connected in the workspace. Switch keys or projects in the Ryze AI app.
- Mistral says a subscription is required
- The PostHog tools work only on an active Ryze AI plan or free trial. Start the trial, then repeat the request.
Terms on this page
- Custom MCP Connector
- What Mistral calls an MCP server that you add by its HTTPS address on the Connectors page.
- MCP
- The Model Context Protocol, an open standard through which AI models reach outside data and apps.
- Personal API key
- A PostHog key that starts with phx_ and signs in the private API as your own user. You choose its scopes and can hold up to 10.
- Scope
- A permission on a PostHog key for one area, such as insights or feature flags. 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, such as a trends chart, a funnel or a retention table.
- 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 address your PostHog account lives on, such as https://us.posthog.com or https://eu.posthog.com.
Sources: Mistral docs: MCP connectors, PostHog personal API keys, PostHog API scopes, PostHog SQL and HogQL, PostHog insights, PostHog cohorts. Checked November 14, 2026.
Frequently asked questions
How do I connect Le Chat to PostHog?
Save a PostHog personal API key and host in Ryze AI under Integrations, pick the project, then add https://connector.get-ryze.ai/mcp in Mistral Vibe (formerly Le Chat). The path is Connectors, + Add Connector, Custom MCP Connector; enter a name such as RyzeAI and the URL, click Connect and finish the Ryze AI sign-in.
What is the PostHog MCP server URL for Le Chat?
For the Ryze AI connector it is https://connector.get-ryze.ai/mcp, the same for every user. PostHog's own hosted server sits at https://mcp.posthog.com/mcp; PostHog's pages do not name Le Chat, and that route was not tried for this guide.
Is there a Le Chat PostHog connector?
Mistral lets an administrator add any remote MCP server by URL as a Custom MCP Connector, and the Ryze AI connector is added that way. Whether Mistral's own directory lists a PostHog connector was not checked.
Does PostHog's own MCP server work with Le Chat?
PostHog says it works with any MCP-compatible client and documents Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf and Zed. It does not name Le Chat or give Mistral steps. Mistral detects OAuth 2.1 with dynamic client registration or a Bearer token, but this pairing was not tried.
Which PostHog connector should I use with Le Chat?
Use the Ryze AI connector when you want queries on one project and a way to keep it read-only by giving the key read scopes only. It has 3 tools and needs a Ryze AI plan or trial. PostHog's own server reaches many more areas, such as session replay and experiments, but PostHog does not name Le Chat.
Do I need a paid Mistral plan?
Mistral's connector docs name no minimum plan. They say an administrator has to add a custom MCP connector, and on Free, Pro and Student plans the account owner is the administrator. Mistral's pricing page marks Custom MCP connectors, labeled beta, on Free, Pro, Team and Enterprise.
Can Le Chat run HogQL queries on PostHog?
Yes. The read tool runs HogQL analytics queries over events, persons and sessions. Ryze AI needs a time window and a row limit of 1,000 at most, so name both in the prompt.
Can Le Chat change my PostHog project?
Yes, if the personal API key has write scopes. The write tool creates or updates insights, dashboards, feature flags and cohorts. Mistral asks before a call that creates, modifies, sends, posts or deletes, so read the prompt before you click Continue.
Can Le Chat delete PostHog objects?
Yes, through the separate posthog__delete tool, when you ask for it explicitly. The deletion is irreversible. For no changes of any kind, use a key with read scopes only, because PostHog then rejects any change.
How do I stop Le Chat from running write tools without asking?
Open Connectors, My Connectors, the Ryze AI card and its Functions tab, and leave Always allow off for the write and delete functions. Mistral advises keeping write functions on manual approval.
Which sign-in does Mistral use for Ryze AI?
Mistral detects it from the URL. Ryze AI uses OAuth 2.1 with dynamic client registration, so there is no client ID or secret to type. You sign in to Ryze AI, choose workspaces and click Allow connection. The PostHog key is saved separately in Ryze AI.
Does it work with PostHog EU Cloud or a self-hosted instance?
Yes. Ryze AI asks for the host with the key: https://us.posthog.com for US Cloud, https://eu.posthog.com for EU Cloud or your own address when self-hosted.
Can I use more than one PostHog project?
Not in one connection. Ryze AI saves one project per connection, and PostHog is not on its list of platforms that support several accounts. Switch by disconnecting and connecting again, or use another Ryze AI workspace for the second project.
Why do the PostHog tools not show up in Le Chat?
Open a new chat first, then click Refresh tools on the Functions tab of the Ryze AI card. If they are still missing, confirm that Ryze AI lists PostHog as Connected, then remove the connector and add it again.
How much does it cost to connect Le Chat to PostHog?
Adding the connector is free, and the PostHog tools need an active Ryze AI plan or trial. Paid Ads is $89 per month with a 7-day free trial, Agency is $279 per month, and annual billing takes 30% off the first year. PostHog's own server is free to connect.