1MCP
1MCP is the unified MCP runtime. 1mcp serve aggregates your MCP servers, and CLI mode adds a thinner agent-facing workflow for Codex, Claude, Cursor, and similar tool-using agents.
Why 1MCP
Most MCP setups eventually hit two kinds of sprawl:
- Configuration sprawl: every client needs its own MCP wiring, auth choices, and filtering rules.
- Agent sprawl: autonomous sessions carry too many tools and schemas into context up front.
1MCP addresses both:
1mcp servegives you one aggregated runtime in front of many MCP servers.- CLI mode lets agents discover tools progressively with
instructions,inspect, andrun. - Static servers can load at startup, while template servers are created from per-client or per-session context.
- Presets, filters, and instruction aggregation keep the same runtime adaptable across clients and projects.
| Approach | Best for | Tradeoff |
|---|---|---|
| 1MCP CLI mode | Codex, Claude, agent loops | Requires a running 1mcp serve instance |
| 1MCP stdio proxy | Maximum compatibility across clients | Still depends on serve, and auth-capable HTTP clients have a more direct path |
| Direct streamable HTTP | MCP-native HTTP clients | No project context, no .1mcprc, and a broader tool surface is exposed directly |
| Custom proxying | One-off compatibility shims | You own discovery, filtering, auth, and runtime lifecycle |
