1MCP AgentOne runtime for MCP, one thinner workflow for agents

Why 1MCP? ​

1MCP solves two related problems at once:

• Configuration sprawl: too many clients each need their own MCP setup.
• Agent context sprawl: too many tools and schemas get injected into long-running agent loops.

The current product model is:

• 1mcp serve is the unified runtime.
• CLI mode is the preferred agent-facing workflow on the unified runtime.
• proxy is the preferred non-CLI path because it keeps project context and works with the widest set of AI clients.
• Direct streamable HTTP remains supported for MCP-native clients that do not need project context.

Use this page to choose a path. If you already know you want a working setup, go straight to Quick Start.

Start Here if You Use an AI Agent ​

This page is for Codex, Claude, Cursor, and similar agent workflows. The default path is: add one real upstream server, start 1mcp serve, run cli-setup, then verify instructions -> inspect -> run.

Start With the Right Path ​

• Want the fastest first success for an agent workflow? Go to Quick Start.
• Want the mental model for instructions, inspect, and run? Go to CLI Mode.
• Want the broadest non-CLI client compatibility with project context? Go to proxy.
• Want to connect an MCP-native client directly to the runtime over streamable HTTP? Go to serve.
• Want runtime details, loading behavior, or templates? Go to Architecture.

5-Minute Setup Preview ​

npm install -g @1mcp/agent
1mcp mcp add context7 -- npx -y @upstash/context7-mcp
1mcp serve

Connect your agent to CLI mode:

1mcp cli-setup --codex
# or
1mcp cli-setup --claude --scope repo --repo-root .

Verify the workflow:

1mcp instructions
1mcp inspect context7
1mcp inspect context7/query-docs
1mcp run context7/query-docs --args '{"libraryId":"/mongodb/docs","query":"aggregation pipeline"}'

This is only the preview path. For prerequisites, success checks, and troubleshooting, continue to the Quick Start guide.

Why This Path ​

• Smaller working surface for agents: progressive discovery avoids dumping the whole tool catalog into context.
• One runtime for many clients: agents, stdio-compatible clients through proxy, and direct HTTP MCP clients can share the same backend inventory.
• Current runtime behavior, not a static proxy model: async loading, lazy loading, templates, instructions, and presets are part of the main system design.

Choose Another Path ​