Mistral AI · CLI

Connect Mistral Vibe CLI to Relay

Give Mistral Vibe CLI a memory it shares with your other AIs. Plans, progress and reviews saved in Mistral Vibe CLI can be picked up by any of the 38 AI tools Relay works with, and the other way round. It takes about two minutes.

How it connects: One command or config entry (MCP)

1. Get your connection link

Sign in to Relay with Google. It's free during the beta.
Click Connect an AI, pick Mistral Vibe CLI, then Create my connection link. Copy it straight away: it's shown only once.
Below, YOUR-KEY stands for your link. The dashboard shows the same steps with your link already filled in.

2. Add Relay to Mistral Vibe CLI

Add Relay

Open Vibe's config file: ~/.vibe/config.toml (on Windows %USERPROFILE%\.vibe\config.toml; create it if it's missing).

Add this at the end. The header line stops Vibe from trying a sign-in Relay doesn't need:

[[mcp_servers]]
name = "relay"
transport = "streamable-http"
url = "https://mcp.relaymemory.app/mcp/YOUR-KEY"
headers = { "X-Client" = "relay" }

Start Vibe (type vibe) and run /mcp. relay should be listed.

Remove Relay (or start over)

Run this (or delete the relay block from config.toml), then add it again if you want a new link:
```
vibe mcp remove relay
```

Can't find a button or option? Ask Mistral Vibe CLI itself

Apps change their menus often. Paste this into Mistral Vibe CLI (with your own link instead of YOUR-KEY), and it will walk you through its current screens.

How do I add a custom MCP server to Mistral Vibe CLI? Please give me short, exact step-by-step instructions for the current version of Mistral Vibe CLI that I'm using: where to click, which options to choose, and where to paste the server address.

The server is called "Relay". It is a remote MCP server using Streamable HTTP, at this address:
https://mcp.relaymemory.app/mcp/YOUR-KEY

It needs no sign-in: no OAuth, no API key and no headers (the key is part of the address).
If Mistral Vibe CLI can't add custom MCP servers on my account or version, tell me that plainly.

3. Test it

Send this in Mistral Vibe CLI. It should answer from your Relay memory:

Pick up my latest plan from Relay.

Make it save on its own

In a Mistral Vibe CLI session, send this once:

In every conversation, store our work in Relay: save new plans, add progress updates as we go, and keep it up to date.

Mistral Vibe CLI asks permission to use Relay. Choose Allow always, so it saves as you work. Deleting always asks you first.
To keep it on in new sessions, add the same sentence to your project's instructions file (for example AGENTS.md).

Using Relay in Mistral Vibe CLI every day

Once added, Relay loads in every session. There's nothing to switch on.
When it asks to run a Relay tool, approve it. Most tools let you always allow it, so it stops asking.
Make it automatic: add this line to your project's instructions file (for example AGENTS.md), and it checks Relay on its own.
```
At the start of a task, check Relay for the latest plan for this project. When you finish, add a progress update to Relay.
```

Things to say in Mistral Vibe CLI:

Save this plan to Relay for the project "My project".

Pick up my latest plan from Relay and continue it.

Save this to Relay with every decision and its reason, and what we tried that didn't work and why.

Add a progress update to Relay for this work.

Review the latest work in Relay and add your review.

Remember in Relay that I prefer short answers.

What's waiting for me in Relay?

Mistral Vibe CLI uses Relay's cloud endpoint, so it works even when Relay isn't running on your PC. Mistral Vibe is Mistral's coding agent for the terminal. For Mistral's chat app (Vibe on the web, formerly Le Chat), use the Le Chat guide.

Connect Mistral Vibe CLI in two minutes

Join the free beta