Best for
- Users with Codex, Claude, Cursor, or similar agents who want to keep MCP as backend but reduce context burden.
- Teams needing consistent MCP configuration across multiple clients and projects.
A
Agent
Community
The unified MCP runtime that aggregates your MCP servers and adds a thinner agent-facing workflow.
GitHub source repository ↗
43FMRS · D
1MCP is a feature-rich unified MCP runtime that aims to manage MCP server sprawl and agent workflows. It offers a powerful CLI mode with progressive tool discovery and supports template servers and centralized configuration. However, it introduces an additional runtime dependency and complexity that may not be suitable for simple use cases or native MCP clients.
1MCP is a unified Model Context Protocol (MCP) runtime that aggregates multiple MCP servers into a single serve process. It provides a CLI mode for progressive tool discovery with instructions, inspect, and run commands, and supports template servers, instruction aggregation, presets, and filters. This server is suitable for users who need centralized configuration, authentication, and runtime lifecycle management across multiple clients and projects.
Tools
instructions
Provides an explanation of the current runtime and recommended flow.
inspect
Discovers only the needed server or tool details.
run
Executes a selected tool after schema inspection.
Setup
Install @1mcp/agent globally: npm install -g @1mcp/agent. Then add an upstream server: 1mcp mcp add context7 -- npx -y @upstash/context7-mcp, and start the runtime: 1mcp serve. In a second shell, connect your agent to CLI mode: 1mcp cli-setup --codex or 1mcp cli-setup --claude --scope repo --repo-root ..
Fit and risk
Not for
- Native HTTP MCP clients that want direct access without project context.
- Simple single-server scenarios where an additional runtime dependency is undesirable.
Required permissions
- May make network connections to upstream MCP servers.
- May read and write local filesystem for configuration and caching.
- May spawn and manage subprocesses (for stdio backends).
Risks and side effects
- As an aggregated runtime, it introduces an extra point of failure.
- May expose a broader tool surface than intended if filters or presets are not configured properly.
- Template server resolution depends on client context and may lead to unexpected behavior.
Troubleshooting
- Ensure `1mcp serve` is running and CLI commands are executed in a second shell.
- Check the `.1mcprc` configuration file for correct setup.
- Verify that upstream servers are reachable and added correctly.
Use cases
Give a coding agent one stable runtime but a smaller working surface.
Share the same MCP inventory across Cursor, Claude Code, Codex, and internal tooling.
Expose context-specific template servers per repo, branch, or session.
Centralize auth, filtering, presets, and runtime lifecycle instead of rebuilding them in ad hoc scripts.
Supported clients
Claude DesktopFull support
CodexFull support
CursorFull support