tool_listLABSCO SUMMARY
The sprawl it fixes is real: every client re-declaring the same twelve servers, and every one of those definitions costing context.
Once you run more than a handful of servers, two problems arrive together — the same configuration duplicated across every client you use, and a tool list too long for any single conversation to carry. An aggregator solves the first cleanly. Whether it solves the second depends on whether it lets you narrow what is exposed, which is what the thinner agent-facing mode is for. Worth checking that behaviour first, because a single endpoint that simply concatenates everything makes the context problem worse, not better.
What it is
A runtime that aggregates the servers you already run and presents them as a single connection. It also offers a thinner agent-facing mode from the command line.
What you get
- One endpoint in front of many servers
- A command-line mode that presents a narrower surface to an agent
- Configuration in one place rather than repeated per client
Requirements
Node, installed from npm. Apache-2.0 licensed.
Setup effort
Follow the published steps — npm install -g @1mcp/agent
USE CASES
01
Configuring once
One endpoint per client instead of a list per client.
02
Keeping the surface narrow
The agent-facing mode rather than the full concatenation.
3 tools
Listed in project docs. Your client may show a different list.
tool_schematool_invokeBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
npm on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @1mcp/agent
1mcp mcp add context7 -- npx -y @upstash/context7-mcp
1mcp serveMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"1mcp": {
"url": "http://127.0.0.1:3050/mcp?app=cursor"
}
}
}Claude Code — HTTP
CLAUDE CODE — HTTP · TERMINAL
claude mcp add -t http 1mcp "http://127.0.0.1:3050/mcp?app=claude-code"Codex
CODEX · TERMINAL
1mcp cli-setup --codexClaude Code — CLI setup
CLAUDE CODE — CLI SETUP · TERMINAL
1mcp cli-setup --claude --scope repo --repo-root .Any MCP client — Windows
First download and extract the packaged Windows executable, following the project's Windows binary installation instructions:https://docs.1mcp.app/guide/installation
ANY MCP CLIENT — WINDOWS · JSON
{
"mcpServers": {
"1mcp": {
"command": "C:\\Tools\\1mcp\\1mcp-win32-x64.exe",
"args": [
"proxy"
]
}
}
}For Windows clients that fail to start npm's 1mcp.cmd shim. C:\Tools\1mcp\1mcp-win32-x64.exe is a sample; yours is the path where you extracted the executable. Like the stdio block, it connects to a running 1mcp serve.
Any MCP client — stdio
ANY MCP CLIENT — STDIO · JSON
{
"mcpServers": {
"1mcp": {
"command": "1mcp",
"args": [
"proxy"
]
}
}
}
