Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@z-code-mcp Orchestrate implementing user authentication with code analysis, code generation, and tests"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for orchestrating multiple Claude Code sessions with HEAD/SUB coordination pattern.
Z-Code MCP enables complex, multi-task coding projects by coordinating multiple Claude Code CLI sessions:
HEAD Phase: Analyzes objectives and creates execution plans
SUB Phase: Executes tasks in parallel with controlled concurrency
Aggregation Phase: Combines results and generates summaries
Related MCP server: claude-session-bridge
npx z-code-mcpFor always getting the latest version:
npx z-code-mcp@latestnpm install -g z-code-mcpAdd to your Claude configuration file:
Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"z-code-mcp": {
"command": "npx",
"args": ["-y", "z-code-mcp@latest"]
}
}
}For testing local changes without publishing:
{
"mcpServers": {
"z-code-mcp-dev": {
"command": "node",
"args": ["C:/path/to/z-code-mcp/build/index.js"]
}
}
}Variable | Description | Default |
| Claude CLI command |
|
| Max concurrent processes (1-10) |
|
| Temp directory for outputs | System temp |
| Keep temp files on error |
|
| Custom templates directory | Built-in |
| Log level (debug/info/warn/error) |
|
Template | Description |
| Analyze existing code structure and patterns |
| Generate new code based on specifications |
| Write tests for existing code |
| Create documentation |
| Security analysis and vulnerability detection |
| Code improvements and refactoring |
| Use custom template |
Once configured, the MCP exposes an orchestrate tool:
{
"objective": "Implement user authentication feature",
"workingDirectory": "/path/to/project",
"tasks": [
{
"id": "analyze",
"type": "code_analysis",
"description": "Analyze current auth implementation"
},
{
"id": "implement",
"type": "code_generation",
"description": "Implement JWT authentication",
"dependencies": ["analyze"]
},
{
"id": "test",
"type": "test_writing",
"description": "Write auth tests",
"dependencies": ["implement"]
}
],
"coordination": {
"strategy": "dependency-based",
"maxConcurrent": 3
}
}# Install dependencies
npm install
# Build
npm run build
# Watch mode
npm run dev
# Run MCP Inspector
npm run inspectornpx caches packages: Use npx z-code-mcp@latest to force latest version
Local development: Use direct path reference for immediate updates after build
MIT
Orchestrate multiple Claude Code sessions with HEAD/SUB coordination. HEAD analyzes the objective, creates an execution plan, spawns SUB processes to handle individual tasks, and aggregates results.
Inputs: tasks (required), objective (required), workingDirectory (required), coordination, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Command center for developers coordinating AI coding agents across projects.
Shared workspace where Claude, ChatGPT, Codex and Grok share files, tasks, decisions and handoffs.
AI work orchestration for plans, tasks, teams, and coding-agent dispatch.
One shared project for a team's coding agents: decisions, a task board and handoffs.
