Mistral's new connector controls turn enterprise AI governance from a checkbox into a dial

Mistral AI today added several upgrades to its Connectors feature, giving enterprises more granular control over how AI agents connect to outside platforms. The update includes enriched admin controls at workspace and org levels, API keys with scoped connector permissions, multi-account connectors, a Connectors Debugger, and support for Connectors in Workflows and Vibe Code. The release follows Mistral's broader enterprise platform push, where owning the full stack rather than just a model is the stated goal.

Controls that match production complexity

The new admin controls layer a two-tier permission model onto what used to be a simple on-off switch. At the workspace level, administrators can give each team different connector access: finance can reach internal databases while engineering gets developer tools and the internet. Tool-level controls go further, blocking a specific action like delete_file on a knowledge base while keeping the rest of the connector live.

API keys can now be scoped to reach only a workspace's shared connectors or private ones, so automated jobs cannot impersonate the developer who wrote them. Paired with service accounts, Mistral says, the system makes sure automated work runs as a defined identity rather than a human's credentials. This matters because agents that run long enough become harder to audit without clear identity boundaries.

Multi-account and multi-step debugging

Multi-account connectors let a single connector hold more than one login, a personal and a work account, for instance, with a default account per task. Each account stores and refreshes tokens independently, so an agent can switch identities without needing a second connector.

The Connectors Debugger, now in public preview, walks a connection through 11 steps from reaching the server to opening the MCP session, logging each one. A failure that once required guesswork, like a broken OAuth token exchange, now surfaces at the exact step it breaks.

Connectors in Workflows and Vibe Code

Connectors in Workflows keep long-running or scheduled jobs from failing due to token expiration. The Workflow definition declares which connectors and accounts it needs, and Mistral Studio resolves those dependencies at launch. Connectors in Vibe Code bring the same governed access to the coding agent: users type /connectors to pick from local MCP servers and approved workspace connectors. That approach aligns with the broader industry shift toward agent operating systems where connectivity governance is baked into the runtime.

Mistral says it is adding connectors continuously, with over 60 integrations now available across categories including knowledge management, analytics, developer infrastructure, and automation. For platforms not in the directory, a custom MCP connector can be built.

Availability

Enterprise controls, Connector Credentials, and Connectors in Vibe Code are generally available now. Connectors Debugger and Connectors in Workflows are in public preview. The full set of features is live in Mistral Studio.