In-depth architectural comparison of the Agent Nexus and Codex Control Plane MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Agent Nexus
Coding Agents · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: No auth required
Codex Control Plane MCP
Coding Agents · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Verdict Summary: Choose Agent Nexus if you need specialized Coding Agents tools running via a hosted cloud SSE transport. Choose Codex Control Plane MCP if your workspace requires Coding Agents integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agent Nexus when:
You need dedicated capabilities in the Coding Agents domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Service-boundary-aware document exchange center for coordinating heterogeneous LLM code agents. Versioned Markdown store, pub-sub notifications, diff-aware updates, and lifecycle stage tracking. Each service registers as a sub-project; agents subscribe to cross-service document changes and receive structured diffs via MCP.
Durable control plane for long-running Codex Desktop tasks. Submit tasks asynchronously, poll operation/workflow state, approve Plan Mode, recover retries, and use hook-backed SQLite history for search and diagnostics.
Category & Scope
Tools & Capabilities Breakdown
Agent Nexus Tools (17)
create_space
Create a Project Space
register_project
Register a sub-project (boundary)
list_projects
List all sub-projects in a space
list_documents
List all documents in a sub-project
get_document
Retrieve a document (latest or specific version)
get_my_updates_with_context
Get unread notifications with diff + full content
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Agent Nexus is categorized under Coding Agents and uses a remote streaming HTTP/SSE transport. In contrast, Codex Control Plane MCP belongs to Coding Agents using local stdio subprocess. Select Agent Nexus when you need capabilities focused on coding agents and Codex Control Plane MCP when you require tools for coding agents.
List known Codex projects from registry, hook history, transcripts, and cached Codex state. Use this before preflight or submit when you need a project reference; later tools accept projectId, project name, or project path and return canonical projectId. Next call codex_preflight_project_run for a concrete project.
codex_list_project_chats
List chats for one project from the bounded read model. Use this to find existing threads before continuation or review. Next call codex_get_chat_status, codex_get_chat, or codex_submit_task.
codex_list_active_chats
List chats that look active from tracked, hook, transcript, or cached evidence. Use this for operator inspection, not for creating retries. Next call codex_get_turn_status or codex_get_operation_status when ids are available.
codex_search_chats
Search chat history through the MCP-owned index and safe fallback sources. Use this for discovery or recovery when ids were lost. Do not use search results as proof that a turn is still active.
codex_get_chat_status
Read lightweight chat status and safe previews. Use this to inspect a known thread without starting live work. Next call codex_get_chat for content or codex_submit_task for a new operation.
codex_get_chat
Read bounded chat content from hook history, transcripts, or legacy fallback. Use this for context recovery and final report inspection. It is not a write path and should not trigger retries.
codex_send_message
Compatibility write for sending a message to an existing Codex thread. Prefer codex_submit_task with operation_type='send_message' for durable long work. In client mode this delegates to the durable queue.
codex_start_chat
Compatibility write for starting a new Codex chat. Prefer codex_submit_task with operation_type='start_chat' for durable long work. In client mode this delegates to the durable queue.
codex_start_plan_workflow
Start a durable Plan Mode workflow and return workflowId immediately. Use this when a plan must be prepared before implementation. Next poll codex_get_workflow_status, then call codex_approve_plan when latestPlan is ready.
codex_start_review_workflow
Start a durable Codex review workflow and return workflowId immediately. Use this for code review tasks. Next poll codex_get_workflow_status for progress and final report.
codex_get_workflow_status
Poll workflow state from storage by default. Use this for Plan Mode, execution, and review workflows. Follow nextRecommendedAction and do not create replacement work unless guidance tells you to.
codex_adopt_workflow_plan
Adopt a valid newer Plan Mode candidate already present in the workflow thread. Use this only when status or diagnostics reports an adoptable plan. Next poll codex_get_workflow_status.