Hosted assistant, Hosted, public HTTPS
Mistral Le Chat WordPress MCP. A Custom MCP Connector.
Mistral Le Chat WordPress MCP setup is one Custom MCP Connector form, and Le Chat works out on its own how the server wants to authenticate. GoBuildWP answers with OAuth, so pressing Connect usually leads straight to your WordPress login. Mistral's documentation now presents the assistant as the Work mode of Vibe, with the older interface kept as Chat (legacy).
Checked against Mistral Le Chat's documentation on 29 September 2026, entries from GoBuildWP Free 1.18.6
Name gobuildwp-your-site-com
Server URL https://your-site.com/wp-json/mcp/wppilot-oauth- Add in
- Connectors, Add Connector, Custom MCP Connector
- Name rule
- An identifier: no spaces or special characters
- Auth
- Detected on Connect: OAuth or HTTP Bearer Token
Setup
Add WordPress as a Le Chat connector
Mistral makes custom connectors an administrator feature. On Free, Pro and Student plans the account owner is the administrator, so an individual can do this alone.
Open Connectors
Go to the Connectors page, press Add Connector and switch to the Custom MCP Connector tab.
Name it as an identifier
Mistral asks for a unique identifier with no spaces or special characters. Use a simple alphanumeric name such as gobuildwpyoursite, and check the form's validation rather than assuming GoBuildWP's hyphenated suggestion is accepted.
Paste the URL and connect
Enter the server URL, add a description if you like, and press Connect. Le Chat inspects the server and offers the matching sign-in.
Authorize on your site
Log in to WordPress as the user this connector should act as and approve. For the token route, choose HTTP Bearer Token and paste the value instead.
Turn it on in a chat
In a conversation, click + or type /, choose Tools and enable the connector. It stays off in chats where you have not enabled it.
Verify the connection before allowing changes
Select Read Only explicitly; the default is Production Safe. Use a dedicated identity with manage_options on a single site, or superadmin on multisite. Match the named tool call, site URL and returned record ID against WordPress.
Use the gobuildwp-your-site-com MCP server in Mistral Le Chat. Do not change anything.
1. Report the active GoBuildWP safety profile.
2. List the abilities this connection can see.
3. Call wppilot/get-site-settings and report the site URL and locale.
4. Call wppilot/list-content for the five newest pages,
then wppilot/get-content on one of them.
5. Name every ability you called and each WordPress ID you read.These setup instructions are not a recorded live-client test. Keep credentials out of repositories, logs and shared files.
Connect screen
The Mistral Le Chat entries GoBuildWP writes
GoBuildWP's OAuth steps give Le Chat a name and the OAuth URL and leave the rest to auto-detection. The access-token steps use the canonical URL and the HTTP Bearer Token method, and tell you to paste the token without the word Bearer because Le Chat adds the scheme. That last detail comes from the Connect screen, not from a captured request: Mistral's page only says the credential travels in the Authorization header, and the token route has not been tested end to end with this client. Treat it as experimental and prefer OAuth.
| OAuth 2.1 | Press Connect and Le Chat runs the sign-in, using dynamic client registration against the site. |
|---|---|
| Access token | HTTP Bearer Token, untested end to end with Le Chat. Useful for one shared service account across an organization, where each member signing in is not wanted. |
Endpoints on your site: /wp-json/mcp/wppilot-oauth for OAuth, /wp-json/mcp/wppilot for tokens and passwords. Through the optional GoBuildWP Cloud instead, every client uses https://app.gobuildwp.com/mcp with the server name gobuildwp, and a personal Cloud token is read from GOBUILDWP_TOKEN where the client supports environment variables.
Server URL https://your-site.com/wp-json/mcp/wppilot
Authentication HTTP Bearer Token
Token wpp_YOUR-ACCESS-TOKENInside Mistral Le Chat
Approvals and per-function switches in Le Chat
Before each tool call Le Chat asks whether to continue, with Continue, Always allow and Decline as the choices. Always allow is remembered per function, and the list lives under My Connectors, on the connector's Functions tab, where each WordPress ability can be set to always allow or left asking.
That gives you two layers that agree when set sensibly: Le Chat asks before calling anything, and GoBuildWP refuses whatever the safety profile or the WordPress role does not allow. A sensible start is Always allow on read abilities such as wppilot/get-content and asking on everything else.
Mistral documents that custom connectors do not yet support dynamic tool discovery, MCP resources or prompt templates. GoBuildWP's abilities arrive as tools, which is all Le Chat needs, but if you add or enable abilities on the site later, reconnect so the new ones appear.
Signs it worked
- Connect succeeded without the invalid-connector error
- The Functions tab lists wppilot/ abilities
- The connector is enabled in this chat under Tools
- A write asks for approval and the site then refuses it on Read Only
From suggestions to saved SEO fields
Saving Le Chat's title and description suggestions
The first conversation produces a better title and meta description for three posts, written in chat. Those fields usually belong to an SEO plugin rather than to the post itself, and GoBuildWP Free reads and writes them for the common ones: wppilot/yoast-get-post-seo and wppilot/yoast-edit-post-seo for Yoast, with matching abilities for Rank Math, SEOPress and All in One SEO. Ask Le Chat to read the current values first, so the before and after sit side by side in the conversation.
Do the first save on a public staging site set to Production Safe, for one post, and leave that edit function on asking in the connector's Functions tab. Then open the post in wp-admin, check the SEO plugin's own panel shows the new values, and find the change with wppilot/list-changes. Always allow is fine for the read functions once you are happy; keep the edit function asking even on production.
- "Read the Yoast fields for the three posts with wppilot/yoast-get-post-seo and show them next to your suggestions."
- "Save your title and description for the first post only with wppilot/yoast-edit-post-seo."
Each member signing in, or one shared bearer token
OAuth can give each member a separate WordPress grant, with manage_options on a single site or super-admin access on multisite. A shared bearer token attributes covered writes to the shared credential and is revoked for everyone at once. GoBuildWP generates Le Chat's token route, but its header behavior has not been tested here. Prefer OAuth; if evaluating a token, verify one authorized read first and limit its scope, profile ceiling and expiry.
When the site changes, reconnect the connector
Le Chat does not discover tools dynamically, and GoBuildWP changes the tool list whenever the site's safety profile or ability switches change, because blocked abilities are taken out of the registry. After moving staging from Read Only to Production Safe, disconnect and connect again, or Le Chat will keep offering the old, shorter list. GoBuildWP Cloud does not name Le Chat among its tested apps; since connectors run from Mistral's cloud and Cloud is reachable over public HTTPS, the Cloud link may work, but confirm it before relying on it.
FAQ
Mistral Le Chat questions
Does Le Chat support OAuth for custom MCP servers?
Yes. It detects the authentication a server wants when you press Connect, and supports OAuth 2.1 with dynamic client registration as well as HTTP Bearer and Basic credentials.
Can Le Chat reach a WordPress site on my laptop?
No. Connectors are called from Mistral's cloud, and Mistral requires HTTPS with a valid certificate. Use a public staging site.
Is Le Chat the same product as Mistral Vibe?
Mistral's current documentation describes the assistant as Vibe's Work mode and keeps the previous interface as Chat (legacy). Connectors are configured the same way in both.
Can I stop Le Chat asking before every WordPress call?
Per function, from the connector's Functions tab. Keep writes asking. GoBuildWP still requires confirmation on destructive and critical calls, but by default the model sets that flag; Le Chat's prompt and the site's A person approves setting are what put a person in the loop.
First task
A first chat that uses Le Chat's approval prompt
Watch the approval prompt for each call. Approve the reads; there should be nothing else to approve.
Using the WordPress connector, change nothing.
Find the three most recent blog posts
(wppilot/list-content), read each one
(wppilot/get-content), and suggest a better title and
meta description for each. Also tell me which
categories they are in (wppilot/list-terms).Troubleshooting
Mistral Le Chat errors and their causes
| Symptom | Cause and fix |
|---|---|
| MCP connection requires additional information or is invalid | Mistral's documented error for a connector it cannot set up. Check the URL is complete, the site answers over HTTPS with a valid certificate, and the name has no spaces. |
| The Add Connector button is missing | Custom connectors are administrator-only. In an organization, an administrator adds the connector or allows members to. |
| Token connection refused with 401 | OAuth is the documented primary route. Treat the token route as experimental: its form and header behavior remain unverified for this client build. Document a token configuration only after a versioned captured-header test, with credentials redacted. |
| New abilities do not appear | Le Chat does not discover tools dynamically. Disconnect and connect again after changing what GoBuildWP exposes. |
| The connector disappeared for everyone | An administrator can disable specific connectors for the whole organization. Ask them to re-enable it. |
Related
Other hosted assistants
- Claude on the web: a custom connector with CIMD sign-in
- ChatGPT: developer mode and per-chat apps
- Perplexity: remote connectors on paid plans
Mistral Le Chat documentation read on 29 September 2026
Add Le Chat as a connector, approve reads only.
Name it like an identifier, sign in with a dedicated account, and set Always allow on reads alone.