Codex Control Plane MCP vs Loki Mode
A side-by-side look at the Codex Control Plane MCP and Loki Mode MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codex Control Plane MCP for coding agents work as a local process; choose Loki Mode for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codex Control Plane MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
codex_list_projects, codex_list_project_chats, codex_list_active_chats.
Choose Loki Mode when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 63/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 125 | 1,096 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 38 | Not listed |
| Full listing | View Codex Control Plane MCP | View Loki Mode |
Tools & capabilities
Codex Control Plane MCP tools 38
codex_list_projectsList 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_chatsList 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_chatsList 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_chatsSearch 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_statusRead 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_chatRead 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_messageCompatibility 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_chatCompatibility 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_workflowStart 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_workflowStart 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_statusPoll 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_planAdopt 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.- +26 more on the listing page
Loki Mode tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Codex Control Plane MCP
{
"mcpServers": {
"aresyn-codex-control-plane-mcp": {
"command": "uvx",
"args": [
"codex-control-plane-mcp"
]
}
}
}
Loki Mode
{
"mcpServers": {
"loki-mode": {
"command": "npx",
"args": [
"-y",
"loki-mode"
]
}
}
}
Frequently asked questions
Codex Control Plane MCP is categorized under Coding Agents and uses a local stdio subprocess. Loki Mode belongs to Coding Agents and uses a local stdio subprocess. Pick Codex Control Plane MCP for coding agents work and Loki Mode for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Codex Control Plane MCP is listed as free. Auth: no auth required. Loki Mode has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aresyn-codex-control-plane-mcp and loki-mode as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codex Control Plane MCP has a quality signal of 63/100 (Good) with 4 views, 0 installs and 125 GitHub stars. Loki Mode has 53/100 (Good) with 2 views, 0 installs and 1,096 GitHub stars.
