Busabase for Mistral Vibe Code CLI

Connect Mistral Vibe Code CLI to Busabase

Mistral AI's terminal coding agent (the `vibe` command, package `mistral-vibe`): Vibe Code is the coding mode of Mistral's Vibe product, and one engine is shared across this CLI, a VS Code extension and Vibe Code Web sessions. It runs interactive or headless (`vibe -p`) sessions with built-in agent profiles, subagents, MCP servers and Agent Skills, against Mistral-hosted models or any OpenAI-compatible endpoint, including local models.

Paste this into Mistral Vibe Code CLI

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Mistral Vibe Code CLI Skills documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole change-request workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

For this agent

Skills follow the open Agent Skills specification: a directory containing a SKILL.md file with YAML frontmatter (name, description, optional user-invocable, disable-model-invocation, allowed-tools — Vibe reads allowed-tools but does not enforce it). Discovery order: custom skill_paths in config.toml, then project ./.vibe/skills/ and ./.agents/skills/ (trusted folders only), then user-level ~/.vibe/skills/ and ~/.agents/skills/. The `npx skills add` installer that SETUP_SKILL.md runs therefore has two Vibe-readable homes; Vibe's own directory is ~/.vibe/skills. Plugins can bundle skills together with MCP servers and are loaded from ~/.vibe/plugins/ (and ./.vibe/plugins/ in trusted folders).

Prefer a connector?

If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.

Mistral Vibe Code CLI MCP documentation

At a glance

Vendor: Mistral AI
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.vibe/config.toml (project: .vibe/config.toml)

Run this

vibe mcp add busabase --url https://busabase.com/api/mcp

Vibe Code CLI runs in your terminal and can execute shell commands and fetch URLs, so the Skill path applies. Install it (curl -LsSf https://mistral.ai/vibe/install.sh | bash), run vibe in your project, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Vibe discovers SKILL.md skills in ./.vibe/skills/, ./.agents/skills/, ~/.vibe/skills/ and ~/.agents/skills/, so the permanent Busabase skills the setup installs are picked up in later sessions.

Prefer a connector?

Add Busabase as a remote MCP server — Vibe starts the OAuth sign-in as soon as it adds an HTTP server without a header or API key:

vibe mcp add busabase --url https://busabase.com/api/mcp

Approve the sign-in in your browser (the callback lands on http://127.0.0.1:47823/callback by default). Or add it by hand in ~/.vibe/config.toml:

[[mcp_servers]]
name = "busabase"
transport = "streamable-http"
url = "https://busabase.com/api/mcp"

[mcp_servers.auth]
type = "oauth"
scopes = ["mcp"]

Busabase only advertises the mcp scope, so either set it as above or leave the scopes empty to accept the server's advertised defaults. Check the connection inside a session with /mcp status; if it reports the server needs authentication, sign in with /mcp login busabase.

Known gotchas

OAuth tokens are stored in the OS keyring, not in config.toml; in headless environments without a keyring (such as CI) Vibe cannot store OAuth tokens — the docs recommend static authentication there, and Busabase also accepts a personal API key as a Bearer token (the api_key_env route). The OAuth callback must reach the machine running Vibe at 127.0.0.1:47823 by default; over SSH, forward the port first (`ssh -L 47823:127.0.0.1:47823 <host>`). Changing a server's url, scopes, client_id or client_metadata_url invalidates its stored tokens — run `/mcp login <name>` again. An administrator can disable MCP entirely with `enable_mcp = false` in admin config, in which case Vibe refuses to add or sign in to MCP servers at all.

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	Mistral Vibe Code CLI	Claude Code	Cursor
Type	Terminal agents	Terminal agents	AI editors
Recommended path	Agent Skill	Agent Skill	Agent Skill
How it connects	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	OAuth (dynamic registration)	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Nov 10, 2026

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.

Browse every agent

Paste this into Mistral Vibe Code CLI

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.