---
title: "Connect while to Mistral Vibe (formerly Le Chat) over MCP in 2026"
url: https://while.sh/en/guides/connect-mistral-vibe/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Connect while to Mistral Vibe, formerly Le Chat, in 2026

Mistral's Le Chat is now called Vibe. Connected to while through an MCP connector, it puts the tools it builds in the conversation on while, with their data, and leaves what matters for you to approve. Here is the connection, step by step.

Mistral Vibe, formerly Le Chat, **builds tools in the conversation**. Connected to while through a **custom MCP connector**, it also puts them on while: it sends the tool's files in its calls, and while builds it, runs its tests, gives it an HTTPS address and watches it (source 3). The connection takes two minutes.

> **The short version.** In Vibe, add a custom MCP connector named while, at https://app.while.sh/mcp, and click Connect. while then opens its authorization page: you choose where Vibe acts and at what level. What matters, like a production release, then waits for a person's approval.

## The connection at a glance

| The moment | What you do |
|---|---|
| Add the connector | Connectors, + Add Connector, Custom MCP Connector |
| Name it | while, with no spaces or special characters |
| The address | https://app.while.sh/mcp |
| Authorize | A while page: the tool or the organization, and the level |

You must be an **administrator** of your Vibe space. On the Free, Pro and Student plans, the account owner is by default (source 2).

## Step 1: add while as a connector

Open the **Connectors** page, click **+ Add Connector**, then the **Custom MCP Connector** tab (source 2). Name it while, with no spaces, and paste while's MCP server address:

```text titre="MCP server address"
https://app.while.sh/mcp
```

Click **Connect**: Vibe detects while's OAuth authentication on its own and guides you to the consent page (source 2).

## Step 2: authorize Vibe

A while page opens. You sign in, then choose where Vibe acts, **one tool or the whole organization**, and its level, **Read, Read and act, or Administer** (source 3).

In Vibe, you also set, function by function, whether Vibe asks for permission on each call, from the connector's Functions tab (source 2).

> You, to your AI: Put the tool you just built on while, with its data, and keep it for the team.

## What Vibe does next

Through the connector, Vibe **puts the tool on while**, reads **logs and errors**, queries **the data** and **rolls back** when a version causes trouble (source 3).

<figure class="illus"><img src="/illustrations/connecter-vibe-autorisation-1200.webp" srcset="/illustrations/connecter-vibe-autorisation-768.webp 768w, /illustrations/connecter-vibe-autorisation-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="Mistral Vibe connected to while: the custom MCP connector on the Connectors page, while's authorization with the choice of tool and level, and a production release waiting for a person's approval" /><figcaption>The connector in Vibe, the authorization in while, and what matters waits for a person.</figcaption></figure>

## What waits for your approval

Some actions wait for a person, and Vibe gives you the link. **A production release, deleting a database, an outside API or an access**: a person in the organization decides (source 3). Your AI never approves.

The credentials of your software stay in while, and Vibe never sees them. The details are on our [security](/en/security/) page.

Once the tool is on while, keep it for your colleagues with [their email account](/en/guides/internal-tool-company-sign-in/), or share it with a client through [a link and a password](/en/guides/share-app-with-password/). The same guides exist for [Claude Code](/en/guides/connect-claude-code/), [Cursor](/en/guides/connect-cursor/) and [Codex](/en/guides/connect-codex/).

## Try it with Vibe

Give this message to Vibe. The trial is **free, with no sign-up**, and your tool has its address **in 3 minutes**.

```text titre="The message to give your AI"
Read while.sh/agents and help me get started with while.
```

## Sources

1. [Mistral, Le Chat becomes Vibe](https://mistral.ai/news/vibe-agent/), 2026-11-19
2. [Mistral, MCP Connectors](https://docs.mistral.ai/vibe/work/connectors/mcp-connectors), 2026-11-19
3. [while, the page for AI tools](https://app.while.sh/agents?lang=en), 2026-11-19

## Questions

### Are Le Chat and Vibe the same product?

Yes. Le Chat has been called Vibe since May 28, 2026, and your conversations, settings and plan carried over (source 1).

### How do you connect while to Mistral Vibe?

Open the Connectors page, click + Add Connector, then the Custom MCP Connector tab. Name it while, paste https://app.while.sh/mcp and click Connect (source 2).

### Who can add a connector in Vibe?

An administrator. On the Free, Pro and Student plans, the account owner is the administrator by default (source 2).

### What permissions should you give Vibe on while?

At authorization, you choose where it acts, one tool or the whole organization, and its level: Read, Read and act, or Administer. Start with a single tool (source 3).

### Does Vibe see my credentials?

No. The credentials of your software stay in while, and calls to an outside API go through while, which adds them.
