How to connect Le Chat to an MCP server

To connect Le Chat to an MCP server, an administrator opens Connectors → + Add Connector → Custom MCP Connector, enters the server details, and completes authentication. Le Chat is now called Vibe↗ (opens in a new tab), and these are Vibe Work controls. MCP is a standard way for an AI app to use an outside tool, including a shared work record such as fenbs.

What do you need before adding the server?

Get the server’s exact connection URL from its owner. It must be reachable over HTTPS with a valid certificate. A local address that only your computer can reach is not the same as a service the hosted assistant can contact. Check that distinction before changing passwords or retrying sign-in.

Adding a custom MCP connector requires an administrator. Mistral says Free, Pro, and Student account owners are administrators by default; an organization administrator controls availability for an organization. Each user then controls function approvals. These are separate responsibilities, as described in the MCP Connectors guide↗ (opens in a new tab).

• Confirm who runs the server and what information you intend to share with it.
• Get the full server URL, including the path supplied by its owner.
• Check which account you will use to sign in and what that account may read or change.
• Choose one harmless read-only task for the first test.

How do you add the custom connector?

1. Open Connectors in the sidebar.
2. Click + Add Connector and choose Custom MCP Connector.
3. Fill in Connector name and Server URL. Add the optional Description if it helps identify the service.
4. Click Connect and complete the authentication requested by the server.
5. In a chat, click + or type /, choose Tools, and enable the connector you want to use.

Mistral documents no authentication, HTTP Bearer or Basic authentication, and OAuth 2.1 with dynamic registration. Use the method the server supports. OAuth is a browser sign-in and approval flow; it does not mean you should paste a password into a chat. The general Connectors guide↗ (opens in a new tab) documents the chat’s Tools control.

These instructions describe the sidebar interface. The cited sources do not establish an identical installation path in the native phone apps. Set up and confirm the connection in the documented interface before depending on it elsewhere.

Which functions should ask before running?

Open Connectors → My Connectors, select the connector, and open Functions. Each function has an Always allow control. Read the function’s purpose before changing it: retrieving a list and editing a record can have very different consequences even when they belong to the same service.

Mistral recommends keeping write actions on manual approval until you trust the connector’s behavior. Approval in the AI app and permission in the outside service are different checks. Write down what the assistant may do for this task, and keep lasting rules in fenbs’s shared work record so another session can read them too.

How do you test that the connection works?

Begin with a result you can recognize without exposing sensitive material. For example, ask the assistant to list a few records in a test area you own. State that the test is read-only and that it must stop before making changes. Compare the returned names with the service itself.

1. Enable only the connector needed for the test.
2. Ask for the narrow read-only task you prepared.
3. Review the requested action and the information it would send.
4. Check the result in the original service.
5. Save whether the test worked and any limit you discovered before trying a larger task.

A successful sign-in proves that authentication completed. It does not prove that every tool works, that the right account was selected, or that the assistant may change every record. Check each action you actually need rather than treating the connection as a blanket approval.

What should you check when setup fails?

• The add control is unavailable: ask the organization administrator whether custom connectors are permitted.
• The server cannot be reached: verify the full HTTPS URL and certificate with the server owner.
• Authentication fails: check that the server supports one of the documented methods and that the intended account can sign in.
• A tool does not appear or behave as expected: check the server’s advertised functions and Mistral’s current limitations.
• A request needs approval: inspect the function’s approval setting before assuming the connection is broken.

Mistral lists dynamic tool discovery, MCP resources, and automatic prompt templates as current limitations. Those terms describe ways a server can expose changing tools, reference material, or reusable prompts. A compatible sign-in does not make unsupported capabilities available. If your goal is to reuse documents instead, see Le Chat Libraries.

A prompt also cannot grant access that the service refuses. The Mistral system prompt guide covers instructions; Claude versus Mistral covers choosing an assistant. Neither replaces testing the actual connector. More connection explanations live in Connect your AI tools.

How to keep connected work with fenbs

Keep the result of the work so you can continue from exactly where you left off, on any device and in any other connected AI. Save the outcome and next step, rather than relying on someone to remember the tool calls.

1. Create a free account.
2. Connect Le Chat to fenbs using Vibe Work’s custom connector controls. See Integrations for connection guidance and use an administrator for setup.
3. Ask the assistant to read the rules and where the work stopped before taking a task.
4. Before stopping, save what changed, what you checked, and the next step. Leave decisions that need a person clearly open.

fenbs is useful when the work should survive a change of chat or assistant. It does not make an incompatible MCP server work or override the server’s permissions. For a single disposable test, the service’s own result may be all you need.