Codex Supervisor MCP vs Forge
A side-by-side look at the Codex Supervisor MCP and Forge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codex Supervisor MCP for coding agents work as a local process; choose Forge for coding agents. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codex Supervisor 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.
Choose Forge when
- You need dedicated capabilities in the Coding Agents domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 48/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 34 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Codex Supervisor MCP | View Forge |
Tools & capabilities
Codex Supervisor MCP tools
No tool names declared yet. Check the project README from the listing page.
Forge 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 Supervisor MCP
{
"mcpServers": {
"codex-supervisor-mcp": {
"command": "npx",
"args": [
"-y",
"codex-supervisor-mcp"
]
}
}
}
Forge
No confirmed install command for Forge yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Codex Supervisor MCP is categorized under Coding Agents and uses a local stdio subprocess. Forge belongs to Coding Agents and uses an install path we have not confirmed yet. Pick Codex Supervisor MCP for coding agents work and Forge 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. Forge has no confirmed install command yet — follow its own setup instructions.
Codex Supervisor MCP has no declared pricing — check the project's own site. Auth: no auth required. Forge is listed as free. Auth: no auth required. 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 codex-supervisor-mcp and tt-wang-forge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codex Supervisor MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 3 GitHub stars. Forge has 51/100 (Good) with 2 views, 0 installs and 34 GitHub stars.