Connectors
Connectors give the Vibe Code CLI access to supported first-party and third-party services from inside a coding session. Unlike MCP servers, which you wire up yourself, Connectors are Mistral-managed integrations.
For the full list of supported connectors and what each one can do, see Connectors in Vibe Work. Vibe Code and Vibe Work share the same integrations.
Connectors vs. MCP servers
Both expose tools to Vibe, but they're operated differently. Pick whichever fits the service you want to connect:
| Connectors | MCP servers | |
|---|---|---|
| Configured by | Mistral, as integrated services | You, in config.toml |
| Auth model | Account or service login | Headers, environment variables, or API keys |
| Discoverability | Curated, listed in the CLI | Anything that speaks MCP |
| Best for | Common services with managed integrations | Custom tools, private servers, experimental tools |
Manage connectors
Connectors are detected and configured automatically. You can list, enable, disable, and inspect them from inside a CLI session.
List all connectors and MCP servers:
/connectors(/connectors is an alias for /mcp.)
From the list, with a connector highlighted:
| Key | Action |
|---|---|
E | Enable the connector |
D | Disable the connector |
Pass a name to inspect the tools exposed by a specific connector:
/connectors fetch_serverStay in control
- Review what each connector can access before authenticating.
- Prefer read-only or scoped access when the task doesn't need write permissions.
- Revoke unused connectors from the relevant service when you no longer need them.