Mistral Vibe: Faster Messages With Cached Connectors and MCP Servers

Mistral VibeOct 26, 2026View original changelog

Mistral Vibe 3.0.3 stopped making users wait on connectors and MCP servers. Messages now run on cached tools while servers refresh in the background, and sessions start with connectors from the last successful load. Vibe also names each connector or MCP server that failed to load, and tells users when /mcp login is needed.

Key Takeaways

Messages run on cached tools while connectors and MCP servers refresh in the background.
Sessions start with the last successful connector load instead of an empty list.
Parallel sessions share one contact per MCP server, cutting duplicate startup work.
Cached MCP tools are refreshed after six hours and kept if the refresh fails.
Vibe names every connector or MCP server that failed to load, including in vibe -p output.
Servers needing login now point to /mcp login, and reauthorization no longer fails a turn.

No more waiting on slow servers

Mistral Vibe 3.0.3 reworks how connectors and MCP servers load so that a slow or unreachable server does not stall the conversation.

Sending a message no longer waits for connectors or MCP servers that already have cached tools. The message runs on the cache while the servers refresh in the background. Only servers with nothing cached yet make a message wait, and only a call to a server that is still loading waits for it. Starting, resuming and switching sessions also no longer waits on unreachable servers.

Smarter loading behind the scenes

The app server started by the CLI and Desktop fetches the connector catalog at startup, before any session opens.
Sessions opened at the same time contact each MCP server once and share the result.
New sessions begin with the connectors from the last successful load instead of none.
MCP tools older than six hours are refreshed in the background, and the cached tools are kept if the refresh fails.

Clearer problems

Vibe now shows a warning naming each connector or MCP server that could not load, including in vibe -p runs and their export. A server without a connector service, such as self-hosted or Private Cloud setups, is treated as having no connectors rather than a failure. If a server turns out to need a login after the session starts, Vibe names the /mcp login command to run. A related fix means a connector that needs reauthorization now reports that authorization is required and the turn continues, instead of failing with "Core rejected durable input".