Mistral Vibe: Connector OAuth Authentication in the MCP Menu
Mistral VibeMistral Vibe v2.9.1 added a Connector OAuth authentication flow directly inside the /mcp menu, allowing developers to authenticate MCP connectors without leaving the CLI. Previously, users had to handle OAuth setup externally; the consent flow is now surfaced inline as part of the connector browsing experience. This reduces the primary friction point for adopting MCP connectors — particularly for OAuth-protected services like GitHub, Linear, Jira, Sentry, and Slack — and brings Vibe CLI's connector experience closer to parity with Mistral's web interfaces.
Sources & Mentions
2 external resources covering this update
In-CLI OAuth Authentication for MCP Connectors
Mistral Vibe v2.9.1 introduced a streamlined OAuth authentication flow embedded directly in the /mcp menu, making it significantly easier to connect external services as MCP connectors without leaving the terminal.
What Changed
Prior to this release, developers who wanted to use OAuth-protected MCP connectors in Mistral Vibe had to configure authentication externally — either by manually obtaining tokens or by going through the Mistral AI Studio web interface. With v2.9.1, the OAuth consent flow is surfaced inline: when a user opens the /mcp menu and selects a connector that requires OAuth, Vibe initiates the authentication process directly, guiding the user through provider authorization without any context-switching.
This is particularly valuable for connectors that integrate with services requiring delegated access, such as GitHub, Linear, Jira, Sentry, and Slack — all of which are first-class integration targets in Mistral Vibe's remote agent stack.
Alignment with the Connectors Ecosystem
Mistral's Connectors system centralizes MCP server registration and makes authenticated integrations available across Mistral products — Le Chat, AI Studio, and now more fully in Vibe. The addition of the in-CLI OAuth flow brings Vibe into closer parity with the web interfaces, where connector authentication has been available for longer. Custom connectors registered with OAuth configuration become persistent native tools for any session, without developers needing to re-implement auth logic or duplicate tokens across environments.
Once authenticated, a connector is available across conversations without re-authorization. Mistral's implementation follows OAuth 2.1 with standard consent screens, meaning it works with any connector that uses the standard OAuth 2.0/2.1 protocol — no custom integration work required beyond the initial setup flow.