z-code-mcp
Related Servers
Alternatives to z-code-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceCoordinates parallel Claude Code agents on shared repositories and orchestrates multiple Claude subscriptions, enabling live session handoff, conflict detection, and remote terminal control.15 npmMIT
- AlicenseAqualityDmaintenanceOrchestrates multiple Claude Code agents across iTerm2 sessions with process-level isolation, enabling collaborative AI development workflows on multiple codebases with task-based inter-agent communication and persistent state management.71MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to launch and supervise multiple concurrent Claude Code sessions in tmux, sending them briefs, reading their progress, answering their prompts, and managing isolated git worktrees.2MIT
- FlicenseNot gradedqualityDmaintenanceCoordinates multiple Claude Code agents to work collaboratively on projects with role-based task management, shared state, and automated code review.7 npm2-
- AlicenseNot gradedqualityDmaintenanceEnables multiple Claude Code sessions to communicate, share state, and coordinate tasks through session management, message passing, and task scheduling, supporting a three-role collaboration workflow.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables multiple Claude Code sessions to communicate and share results automatically, with optional orchestration for hands-off workflow coordination.4 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined.
Single tool named with a verb ('orchestrate'), consistent with a command-style action. No pattern inconsistency possible.
A single tool for a server that coordinates multiple sessions is borderline thin. While the tool itself is non-trivial, the server would benefit from additional tools for session management, making the count slightly low for its apparent scope.
The tool set is severely incomplete. The server's purpose implies managing multiple Claude Code sessions, but there are no tools for creating, listing, monitoring, or terminating sessions—only a single orchestration tool that attempts to handle everything.