mistral-vibe-mcp
Related Servers
Alternatives to mistral-vibe-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to spawn and control long-lived local coding-agent sessions, including turns, mid-turn steering, approvals, user prompts, status, cancellation, and opt-in live event streaming.8 npmBSD Zero Clause
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to submit code review tasks to locally installed AI coding CLI agents, continue sessions, query progress, handle stop requests, and retrieve results and artifacts using the user's own authenticated accounts.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code to delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions that resume across calls.12 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables any MCP-compatible client to run reusable, Markdown-defined coding agents (such as reviewers, test writers, or investigators) through a configurable coding CLI backend, returning results into the same conversation. Agent definitions and backend/model settings can be shared across clients, and sessions can persist across multiple calls for longer work.315 npmMIT
- AlicenseBqualityBmaintenanceEnables launching and supervising local Codex and Claude Code agent sessions and one-shot tasks, exposing run, list, stop, and output operations over MCP with session-scoped permissions and sandbox controls.2336 npm1MIT
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.