Guides

Connect Mistral to Nawame: a step-by-step guide

Short answer

In Mistral’s Le Chat, open the Connectors page, add a custom MCP connector, give it a name, paste the address https://hub.nawame.eu/api/mcp and click Connect, then enter the code sent to your e-mail. You need to be an administrator: that comes from Mistral’s documentation as read on September 30, 2026.

A copper thread-key slides into a square glass socket; the amber thread coming out of it passes through a square glass window before reaching a grey stone block.

Le Chat, Mistral’s assistant, can connect to remote MCP servers through custom connectors. Nawame is one such server: once it is plugged in, Mistral can look up and record working context in your Nawame memory. This guide follows Mistral’s official documentation on MCP connectors (read on September 30, 2026) together with Nawame’s own connection procedure.

Menu names and the layout of the interface keep moving: Mistral’s documentation itself mentions a “Work” space and a “Chat (legacy)”. If something does not match your screen, Mistral’s page wins.

What you need

  • Administrator rights. Mistral reserves custom connectors for administrators. On the Free, Pro and Student plans, the account owner is the administrator by default. In a shared workspace, ask whoever administers it.
  • A Nawame account, or the ability to create one. It is created on first access if it does not exist (create an account).
  • The server address, a single one, path included: https://hub.nawame.eu/api/mcp
  • A mailbox you can open, because Nawame sends a six-digit code.

Nothing to install: Nawame is a remote MCP server (streamable HTTP) with OAuth 2.1 authorization. It is called from the AI provider’s cloud, not from your machine, which is why the address is public.

Add the custom connector

In Le Chat, open the Connectors page. Click “+ Add Connector”, then pick the “Custom MCP Connector” tab. Everything below happens there.

If you cannot see that button, administrator rights are the first thing to check. Mistral also urges you to connect trusted servers only. That applies to Nawame like any other, and you can judge for yourself with the security and documentation pages.

Name, address, connection

The form asks for three things:

  • A name. Mistral expects a unique identifier, with no spaces or special characters. nawame works fine.
  • The server URL, in full: https://hub.nawame.eu/api/mcp. When there is an error, this is the first thing Mistral tells you to check (more on that below).
  • A description, optional.

Click “Connect”. The platform detects which authentication method the server uses: none, a Bearer or Basic token, or OAuth 2.1 with dynamic client registration, with a guided consent flow. Nawame falls in the last group, so you normally have no ID or secret to copy.

Authorize with the code sent by e-mail

During the consent flow, Nawame sends a six-digit code to your e-mail. Type it in. If you did not have an account, it is created at that moment.

What Mistral then receives from Nawame is limited to what your account is allowed to see: the AI never exceeds your rights. A key can even be restricted to an organization or to a folder.

Set permissions per function

Once the connector is added, go to “My Connectors”, open the connector’s card, then the “Functions” tab. Each function has an “Always allow” switch.

Mistral separates read functions (lower risk) from write functions (higher risk), and recommends keeping manual approval for writing until you trust the setup. A cautious arrangement is therefore to always allow a few reads, and to approve by hand anything that writes into your memory.

One honest note: we do not list Nawame’s functions here, because what you see depends on what your client displays and what your account allows. Read the names on offer, and if one means nothing to you, leave manual approval on.

Check that it works

Open a conversation where the connector is on. Here are three checks, from the simplest to the most useful. Nawame’s trigger phrases are written in French, and that is what we document, so try them as they are. We have no official English wording.

  1. Ask what the AI sees. “Which Nawame tools do you have?” A vague answer proves nothing: look at the “Functions” tab instead.
  2. Start a memory. « Active Nawame » opens a memory and starts saving as you go. Imagine a team lead preparing a hire: “We open the position internally first, because two people asked to move up. Keep that as a decision.”
  3. Read it back. « Qu’as-tu retenu ? » asks the AI to reread what it has saved since the start of the exchange. And in a fresh conversation, « ouvre NW-XXXXXX » (with the topic’s anchor code, shaped like NW-2ACRFY) picks the topic back up.

« N’enregistre plus » stops the saving, and what is written stays. In a one-off conversation with no lasting project, Nawame does nothing, which is normal.

If it does not work

  • The message “MCP connection requires additional information or is invalid”. Mistral recommends checking the endpoint URL, exact path included. Copy https://hub.nawame.eu/api/mcp in full, with no stray space or trailing slash.
  • The name is refused. Use an identifier with no spaces or special characters, and one that does not exist yet.
  • Nothing shows up in the tools. Restart or refresh the connector, or create a new one with the same address. Some chat clients show a shorter tool list than code-oriented clients.
  • A screen asks for a client ID and secret. Mistral’s documentation describes dynamic registration, and we go no further than that. If your screen does ask, Nawame’s fallback is the fixed OAuth client: My account, Advanced section, “Fixed OAuth client” (the detailed procedure is in the ChatGPT tutorial).
  • You want to stop everything. Disconnecting Nawame from an AI client deletes neither the account nor the memory.

Current limits

  • Administrator required. Without the rights, you cannot add the connector. We say nothing about a paid plan, because Mistral’s documentation does not mention one.
  • Incomplete custom connectors. Mistral says its custom MCP connectors do not yet handle the whole protocol: dynamic tool discovery, resources, automatic prompt templates. Some capabilities of an MCP server may therefore not show up.
  • A moving interface. “Work”, “Chat (legacy)”, tab names: all of it evolves, and this page dates from September 30, 2026.
  • A trusted server, for you to judge. Mistral urges you to connect trusted servers only: weigh it using the pages linked above.
  • Sovereign mode. Stronger privacy can reduce what the server can process, and therefore some features.

Where to go next

Connecting is the easy part. The rest is habits: what to keep, when to write nothing, how to pick a topic back up. Our tutorial on using Nawame on a long-running project shows an example spread over several weeks. And if you work with Mistral and another AI on the same topic, how to move project context from one AI to another explains when a plain brief is enough. The Grok tutorial follows the same principle, with its own quirks.

Your next prompt should not have to contain your whole story.

Start building a memory your AI tools can find again when it matters.

Start free