Is this still called Le Chat?

No. Mistral renamed Le Chat to Vibe on August 12, 2026. The `chat.mistral.ai` URL is unchanged and existing accounts, plans, and conversations carried over automatically. If you see "Le Chat" in an older screenshot or search result, the product is the same one now called Vibe.

Do I need a paid Mistral plan to add a custom MCP connector?

Mistral's documentation doesn't state a plan restriction on the Custom MCP Connector feature itself — it only requires administrator access. On Free, Pro, and Student plans the account owner is the administrator by default, so a Free-plan account owner can add one. Team and Enterprise plans need an admin to add it. If your account can't find the option, check with your workspace admin before assuming it's a plan gate.

How to Add a Remote MCP Server to Mistral Vibe (formerly Le Chat)

Q: Why did tools from my server stop showing up after I added new ones?

Mistral's docs list dynamic tool discovery as a current limitation of custom MCP connectors — the tool list captured at setup doesn't update on its own when the server changes. Mistral's docs don't describe a dedicated refresh button for this; the documented Functions tab covers permissions, not resyncing the list. Removing and re-adding the connector is the direct way to pick up a changed tool set.

How do I add a custom MCP server to Vibe?

Open the Connectors page, click + Add Connector, switch to the Custom MCP Connector tab, enter a connector name and your server's URL, and click Connect. Vibe detects the server's authentication method on its own — no separate OAuth setup step, API key field, or config file to write by hand, unless your server requires a Bearer token or Basic Auth header, which Vibe also supports.

A naming note: Le Chat is now Vibe

Mistral renamed Le Chat to Vibe on August 12, 2026. Your account, plan, and conversation history moved over automatically, and chat.mistral.ai is still the address you use. Mistral's help center describes three modes at the rename: Vibe Work (the productivity mode Le Chat used for multi-step tasks, on web and mobile), Vibe Code (a CLI, VS Code extension, and web interface for developers), and Vibe Chat (the turn-based conversational mode Le Chat was known for).

That three-mode split didn't stay fixed. Mistral's product documentation notes that, starting September 22, 2026, Chat and Work merged into a single experience — one place for every conversation, with a fast/think toggle setting how deep Vibe goes rather than which tab you're in. Code remains separate. Custom MCP connectors live under what Mistral's docs still label Work, so if your account has migrated to the unified experience, "Work" is less a tab you click and more the umbrella the Connectors feature sits under. Enterprise organizations are on a rolling migration — an admin can pick the date or trigger it early — so what you see may depend on your organization's migration state.

Prerequisites

A Mistral account. Mistral's documentation doesn't state a plan gate on the Custom MCP Connector feature; it does require administrator access
Administrator access. On Free, Pro, and Student plans, the account owner is the administrator by default, so you can add a connector yourself. On Team and Enterprise plans, an admin adds it
Your MCP server's URL, reachable over HTTPS with a valid TLS certificate
If your server requires credentials: know whether it uses OAuth 2.1, a Bearer token, or Basic Auth — Vibe detects which one automatically once you provide the URL, but it helps to know what to expect

Step-by-step setup

1. Open the Connectors page

Go to chat.mistral.ai, and find Connectors under Work.

2. Add a custom connector

Click + Add Connector
Switch to the Custom MCP Connector tab
Fill in the fields:
- Connector name — a unique identifier; no spaces or special characters
- Server URL — the full URL of your MCP-compatible server
- Description (optional) — a short note on what it does
Click Connect

3. Let Vibe detect authentication

Mistral's platform checks the server URL and picks one of three methods on its own:

No authentication, for public or trusted internal servers
HTTP Bearer Token / Basic Auth, for servers that require credentials in the Authorization header
OAuth 2.1 with dynamic client registration, for servers using standard OAuth delegated access

If the server needs OAuth or a Bearer/Basic credential, Vibe walks you through the consent or credential step right after you click Connect.

4. Set per-function permissions

After the connector is live, every one of its functions is available, but you control whether Vibe asks before calling each one:

Go to Connectors and open the My Connectors tab
Click the connector's card
Open the Functions tab
Toggle Always allow for functions you want pre-authorized

Mistral's documentation splits functions into two risk tiers and recommends handling them differently: read functions (listing, searching, fetching data) are lower risk and reasonable to pre-authorize if you use them often; write functions (sending, creating, modifying) are higher risk, and Mistral's own guidance is to keep those on manual approval until you trust the connector's behavior.

Per-function permissions are set by each person individually — adding the connector in the first place is the admin-only step; deciding what it can do without asking is not.

A current limitation: tool lists don't refresh on their own

Mistral's documentation lists three things custom MCP connectors don't support yet: dynamic tool discovery, Resources, and automatic prompt templates. In practice, that means the tool list Vibe captured when you connected the server won't update by itself if the server later adds, removes, or renames tools.

Mistral's docs don't describe a dedicated "refresh" control for this — the Functions tab documented there governs the Always allow toggle, not resyncing the tool list. If a tool you expect isn't showing up, removing the connector and adding it again re-registers the current tool set from scratch.

Troubleshooting

Problem	What to check
"MCP connection requires additional information or is invalid"	Four things, per Mistral's docs: the endpoint path (some servers use `/mcp`, others `/sse` — Streamable HTTP is the current standard); server reachability over HTTPS with a valid TLS certificate; authentication (an OAuth server should return a 401 with a `WWW-Authenticate` header, an API-key server should return 200 on a valid request); and the MCP handshake — the server must respond correctly to the `initialize` JSON-RPC call
The connector name is rejected	Connector names can't contain spaces or special characters
Tools are missing or out of date	Custom connectors don't do dynamic tool discovery yet. Remove and re-add the connector to pick up the current list
"+ Add Connector" isn't there	This is an administrator-only action. On Free, Pro, and Student plans the account owner is the admin by default; on Team and Enterprise, ask your workspace admin
Vibe asks for approval on every call	That's the default for a function until you set it otherwise. Toggle Always allow per function under My Connectors → your connector → Functions

Mistral also documents a way to test a server before configuring it in Vibe, using the MCP Inspector, plus a few direct curl checks: a HEAD request for reachability, a Bearer-token request to confirm API-key auth, and a POST of the initialize JSON-RPC call to confirm the handshake.

What's not confirmed here

Mistral's documentation doesn't state, one way or the other:

Whether connector setup specifically (as opposed to using an already-connected server in a conversation) works from the Vibe mobile apps. The docs confirm Work mode itself is available on iOS and Android
Whether Team and Enterprise admins have a workspace-level on/off switch for MCP connectors generally, separate from the admin-only step of adding one

Treat those as open questions rather than settled behavior, and check your own account's UI if any of them matters to your setup.

A worked example

With a real server — Tempreon, a hosted MCP server that carries your context across every AI tool you connect — the Server URL field takes:

https://api.tempreon.com/functions/v1/tempreon-mcp/mcp

Vibe detects Tempreon's OAuth 2.1 with dynamic client registration automatically, so the only manual step is completing the browser consent flow: sign in, review the request, and approve. From there, a read function like session_start is a reasonable candidate for Always allow, since it only reads; something that writes, like remember, is worth leaving on manual approval until you've seen how it behaves.

The account-holder walkthrough, with the exact field values, is in the Vibe setup doc.