-
licenseNot graded
qualityNot graded
maintenanceEnables AI agents to branch, score, prune, and merge conversation strands with provenance and timeline export. Provides MCP tools and resources for managing parallel exploratory strands.
-
conversation-branch
by qddfxp
Related Servers
Alternatives to conversation-branch
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables git-style version control for agent conversation and task traces, allowing checkpoints, checkout/rollback, and markdown export via MCP tools.-
- AlicenseAqualityAmaintenanceEnables chatbots to interact with a global goals engine, allowing them to declare goals, manage branches, and evaluate outcomes through MCP tools.121MIT
- FlicenseNot gradedqualityDmaintenanceEnables parallel implementation of tasks using git worktrees, allowing you to create multiple variants of a solution, evaluate them side-by-side, and select the best one.2-
- AlicenseNot gradedqualityAmaintenanceEnables enqueuing coding-agent branches and managing a local-first merge train with gated validation, explicit approval, and atomic Git ref updates through MCP.507 PyPI5MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to retrieve Git-backed project context, handoff packages, progress, and next steps, and to append validated progress events with matching project-record commits. This supports visible agent progress, resumable work, and safe handoffs while keeping high-risk actions outside the MCP surface.MIT
TDQS
A3.7/5.0
Scored across 15 tools
Disambiguation4/5
Most tools have clearly distinct purposes: status/check/log all inspect but target different aspects (state, health, timeline). diff/compare are separable as single-branch vs multi-branch analysis. Only minor boundary overlap exists between status and check, but descriptions clarify the distinction.
Naming Consistency5/5
All tools use the unified cb_ prefix followed by a short imperative verb (rename, status, check, log, diff, compare, init, branch, checkout, note, discard, promote, rollback, export, verdict). The pattern is completely consistent and predictable.
Tool Count5/5
15 tools is at the upper boundary of the ideal range, but each tool maps to a distinct operation in the branch lifecycle: init, create, inspect, modify, archive, promote, rollback, export, and verdict review. No tool feels redundant or unnecessary for the stated domain.
Completeness4/5
The surface covers the full branch workflow: creation, checkout, status, health checks, timeline, diffs, comparisons, naming, notes, discard, promotion, rollback, export, and external verdict ingestion. The only notable gap is the lack of a dedicated tool to update or edit the branch PROMPT itself, though that may be intentionally left to direct file editing.
Maintenance
ActivityMaintained
ResponsivenessNo issues