Mistral Vibe: MCP OAuth Authentication Commands and OS Keyring Credential Storage
Mistral VibeMistral Vibe v2.17.0 introduces dedicated /mcp login, /mcp logout, and /mcp status commands for managing OAuth authentication flows directly from the CLI, eliminating the need to handle MCP server credentials manually. API credentials are now stored securely in the OS keyring (system keychain on macOS/Linux/Windows), replacing plaintext config file storage. The release also adds a two-column completion popup for slash commands to improve discoverability, and diff output now highlights all occurrences rather than just the first match.
Sources & Mentions
2 external resources covering this update
MCP OAuth Authentication Commands
Mistral Vibe v2.17.0 ships dedicated commands for managing OAuth authentication with MCP (Model Context Protocol) servers directly from the CLI. The new /mcp login, /mcp logout, and /mcp status commands let you initiate an OAuth flow, clear stored sessions, and inspect the current authentication state for each connected server.
Previously, connecting to an MCP server that required OAuth meant handling credentials and tokens by hand. The new commands wrap the full flow, so you can authenticate against a server and confirm its status without leaving the CLI.
OS Keyring Credential Storage
API credentials are now stored in the operating system keyring instead of a plaintext configuration file. On macOS, Linux, and Windows, Vibe uses the native system keychain to hold tokens and secrets at rest. This removes a long-standing source of accidental credential leakage from config files checked into version control or shared across machines.
Completion and Diff Improvements
The slash command completion popup now renders in two columns, making the available commands easier to scan and discover at a glance. Diff output has also been improved: highlighting now covers every occurrence of a changed segment on a line rather than stopping at the first match, so multi-change lines are easier to read at a review.