mistral-vibe-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIBE_BIN | No | Path to the Vibe CLI binary if it is not available on PATH. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vibe_runB | Start a new Mistral Vibe coding-agent session with a prompt in a project directory. Returns parsed JSON output, session id, exit classification, and a cost/turn summary when available. |
| vibe_resumeA | Continue a previous Vibe session. Provide session_id to resume a specific session (--resume), or continue:true (default when no session_id) to continue the last session for the directory. |
| vibe_manageA | Operational helper for the Vibe CLI: status (installed? version), install, or update via |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct lifecycle phase: starting a session (vibe_run), continuing one (vibe_resume), and CLI maintenance (vibe_manage). There is no overlap — run vs resume is clearly separated by whether a new prompt/session or an existing session is involved.
All three tools use a consistent vibe_<verb> snake_case pattern (vibe_run, vibe_resume, vibe_manage). Names are short, readable, and predictable.
Three tools is on the thin side but well-matched to a focused CLI wrapper: launch, continue, maintain. Nothing extraneous, though a couple more operations could reasonably be added.
The core agent-session lifecycle (start, resume, install/update/status) is covered, which handles the main workflows. Minor gaps exist — no session listing, cancellation/kill of a running session, or history retrieval — but agents can work around these via run/resume output.