Nexus Mcp
Orchestrate Codex, Claude, and OpenCode CLI agents as parallel MCP tools from one host session while you build multi-agent workflows.
Overview
Nexus MCP is a MCP server for the Build phase that invokes Codex, Claude, and OpenCode CLI agents as tools with parallel execution support.
What is this MCP server?
- Invokes Codex, Claude, and OpenCode CLI agents as MCP-callable tools
- Supports parallel execution across multiple agent subprocesses
- PyPI nexus-mcp v1.0.0 with uvx and explicit Python 3.13 runtime positional args
- Stdio transport for drop-in registration beside other MCP servers
- Useful for fan-out tasks—reviews, probes, and multi-perspective codegen—without manual terminal juggling
- Published version 1.0.0 on PyPI identifier nexus-mcp
- Stdio transport; runtimeHint uvx with required Python 3.13 positional args
- Repository: github.com/j7an/nexus-mcp
Community signal: 4 GitHub stars.
What problem does it solve?
Running several CLI coding agents manually breaks flow—you lose parallelism and spend time context-switching between terminals instead of shipping.
Who is it for?
Power users composing multi-agent local workflows who already have Codex, Claude, or OpenCode CLIs installed and authenticated.
Skip if: Beginners who only use one in-IDE chat and do not want to manage Python 3.13, uvx, and multiple CLI credentials.
What do I get? / Deliverables
After you register Nexus, your host agent can dispatch and parallelize sub-agent CLIs as MCP tools from a single session.
- MCP tool surface that runs subsidiary CLI agent jobs from your primary session
- Parallel multi-agent task fan-out without manual terminal multiplexing
Recommended MCP Servers
Journey fit
Nexus sits in Build because it composes how you run other coding agents during implementation—not a launch or growth distribution tool. Agent-tooling captures its role as meta-MCP: your primary agent delegates work to secondary CLI agents through standardized tools.
How it compares
Agent orchestration MCP layer, not a single-model chat skill or a cloud-hosted agent marketplace.
Common Questions / FAQ
Who is Nexus MCP for?
It is for solo builders and advanced agent users who want their main MCP client to call Codex, Claude, and OpenCode CLIs as sub-tools, often in parallel.
When should I use Nexus MCP?
Use it during Build when you need delegated coding or review runs across multiple local agents without manually spawning each CLI yourself.
How do I add Nexus MCP to my agent?
Install nexus-mcp from PyPI via uvx with the required Python 3.13 positional runtime arguments, add the stdio MCP server entry in your client, and ensure underlying CLI agents are on your PATH and logged in.