A
licenseA
qualityB
maintenanceEnables Claude Code to run cursor-agent tasks in isolated git worktrees, manage asynchronous and parallel jobs, review diffs, and safely apply changes back to the repository.
16
16 npm
MIT
vibe-mcp
by idaho06
Related Servers
Alternatives to vibe-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables Codex to delegate bounded engineering jobs to Claude Code CLI in isolated Git worktrees with strict security and allowance pacing.MIT
- AlicenseAqualityDmaintenanceEnables Claude to create, manage, and clean up git worktrees automatically, including dependency installation and GitHub PR creation.5MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude to orchestrate opencode worker sessions by starting tasks, tracking status, sending follow-up messages, and managing git worktrees for review, merge, or discard.MIT
- AlicenseNot gradedqualityCmaintenanceTurns Claude Code into an engineering project manager by orchestrating feature development with isolated Git worktrees, structured task validation, and approval-gated integration.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to delegate coding tasks to a worker CLI, handling actual code modifications and command execution while Claude supervises and verifies results.-
TDQS
A3.9/5.0
Scored across 5 tools
Disambiguation5/5
Each tool maps to a distinct lifecycle phase: submit queues work, wait blocks for completion, result inspects the outcome, apply stages or discards changes, and cancel aborts a job. The boundaries are reinforced by descriptions that cross-reference the natural workflow (submit -> wait -> result -> apply), leaving little room for misselection.
Naming Consistency4/5
All tools share a consistent vibe_ prefix with single-word suffixes, which is predictable and readable. The minor deviation is that four names are verbs (submit, wait, cancel, apply) while vibe_result is a noun, though that is idiomatic for an inspection tool.
Tool Count5/5
Five tools is well-scoped for a job-delegation lifecycle, and each one earns its place with no redundant overlap. Nothing feels thin because wait with timeout=0 doubles as a status poll, and nothing feels padded.
Completeness4/5
The surface covers the full lifecycle: enqueue, await, inspect (summary, diffstat, diff, cost, scope violations), apply/discard, and cancel. Minor gaps remain, such as no dedicated job-listing/history tool for finished jobs and no way to un-apply a staged squash without manual git work, but these are workable.
Maintenance
ActivityMaintained
ResponsivenessSyncing