Mistral Vibe: Add and Remove MCP Servers via CLI Commands
Mistral VibeMistral Vibe introduced dedicated vibe mcp add and vibe mcp remove commands, letting developers register or remove remote MCP servers directly from the CLI instead of hand-editing config.toml. Shipped in v2.23.0, the change extends Mistral Vibe's growing set of first-class MCP management commands, joining the existing /mcp login, /mcp logout, and /mcp status flows added in earlier releases. It lowers the barrier to connecting external tools and data sources to an agent session, particularly for developers who previously found manual TOML editing error-prone.
Key Takeaways
- New CLI commands
vibe mcp addandvibe mcp removelet developers register or delete remote MCP servers without touchingconfig.toml. - Shipped in v2.23.0, released 2026-07-28, alongside a major internal JSON-RPC 2.0 app-server refactor.
- Complements existing MCP tooling, joining the
/mcp login,/mcp logout, and/mcp statuscommands added in earlier releases. - Reduces manual TOML editing, a workflow that was previously error-prone when wiring up MCP integrations by hand.
- Scoped to remote servers in this release; local/stdio MCP server configuration still requires manual
config.tomlentries. - Part of a broader release that also introduced OS-native shell tools in A/B testing and an auto theme that follows terminal/OS appearance.
Sources & Mentions
2 external resources covering this update
Managing MCP Servers Without Touching config.toml
Mistral Vibe's v2.23.0 release added two new top-level CLI commands, vibe mcp add and vibe mcp remove, for managing remote MCP (Model Context Protocol) servers. Previously, wiring up a new MCP server required manually appending a [[mcp_servers]] table to config.toml, specifying transport type, URL, authentication details, and other fields by hand. That manual editing process was easy to get wrong, especially for developers who were not already familiar with the exact TOML schema Mistral Vibe expects.
With the new commands, adding a remote MCP server becomes a single CLI invocation rather than a text-editing exercise. vibe mcp remove provides the equivalent teardown path, letting developers cleanly deregister a server without hunting through the config file to delete the right block. Together, the two commands round out MCP server lifecycle management directly from the terminal.
Building on Existing MCP Tooling
This release builds on MCP-related CLI work Mistral Vibe shipped earlier in 2026. The /mcp login, /mcp logout, and /mcp status slash commands, introduced to handle OAuth authentication flows for MCP servers, already moved credential management out of manual config editing and into the CLI. The /mcp menu also surfaces connector state, flagging servers that still need authentication or setup. The addition of vibe mcp add and vibe mcp remove extends that same philosophy, config-as-commands rather than config-as-file-editing, to the act of registering a server in the first place.
Why It Matters
MCP has become the primary way Mistral Vibe (and comparable coding agents) connect to external tools, databases, and services beyond their built-in toolset. As more developers wire multiple MCP servers into a single agent session, friction in the setup process compounds. Turning server registration into a scriptable, discoverable CLI command reduces that friction and makes it easier to document, share, and automate MCP setup across a team, rather than asking every developer to copy and edit raw TOML by hand.
The same v2.23.0 release also shipped an OS-native shell tools option currently gated behind an [A/B testing] flag, an auto theme that follows terminal or OS appearance, and a substantial internal refactor introducing a JSON-RPC 2.0 app server as the shared runtime layer behind the TUI, programmatic (-p) mode, and ACP. Those changes are either still experimental or primarily architectural, so they were not treated as standalone changelog-worthy features in this review.