Use case · Claude Code
Every MCP server in Claude Code, behind one endpoint.
Point Claude Code at a single onemcp portal instead of wiring up server after server. One `claude mcp add`, and your whole toolset is available — without stuffing hundreds of tool definitions into every prompt.
Connect Claude Code in three steps
- 1
Create a portal
Group the MCP servers you want into a onemcp portal and authenticate each one once.
- 2
Add one command
Run a single `claude mcp add` with your portal URL — no per-server config in Claude Code.
- 3
Let the agent script
Claude Code discovers tools on demand and calls them through Code Mode, in one round-trip.
Run in your terminal:
claude mcp add onemcp --transport http https://portal.onemcp.dev/mcp
Why route Claude Code through onemcp
One endpoint, every tool
Swap or add upstream servers in the portal; Claude Code never needs reconfiguring.
Credentials stay host-side
Native upstream OAuth and tokens live in the portal, never in your Claude Code config.
A lighter context window
Three meta-tools replace hundreds of definitions, so Claude Code spends its context on your task.
Give Claude Code its tools in one line.
Spin up a portal, run one command, and let Claude Code do the rest.