Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @1mcp/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add 1mcp-agent -- npx -y @1mcp/agent@0.39.9Execute em um terminal.
{ "mcpServers": { "1mcp-agent": { "command": "npx", "args": [ "-y", "@1mcp/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
Abrir1MCP 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.
Most MCP setups eventually hit two kinds of sprawl:
1MCP addresses both:
1mcp serve gives you one aggregated runtime in front of many MCP servers.instructions, inspect, and run.This page is optimized for AI agent users. The 5-minute outcome is simple: start a real 1mcp serve runtime, connect your agent with cli-setup, then verify the instructions -> inspect -> run workflow.
You — setup: install 1MCP, add one upstream server, and start the runtime:
npm install -g @1mcp/agent
1mcp mcp add context7 -- npx -y @upstash/context7-mcp
1mcp serve
You — client setup: in a second shell, connect your agent to CLI mode:
1mcp cli-setup --codex
# or
1mcp cli-setup --claude --scope repo --repo-root .
AI agent — after startup: follow this workflow, skipping instructions if hooks already delivered the current instructions. Keep the runtime above running; you do not need to repeat these agent commands manually. Verify that startup delivers guidance and establishes session ownership. With a named or implicitly discovered local runtime, supported Codex sessions resolve their owner and assigned project automatically. Claude and hosts without automatic owner lookup add their own bootstrap --project-owner <own-file> to the commands below; each worker uses its own credential.
# Only if current target guidance is missing or needs refreshing:
1mcp instructions
1mcp inspect context7
1mcp inspect context7/query-docs
1mcp run context7/query-docs --args '{"libraryId":"/mongodb/docs","query":"aggregation pipeline"}'
If you want the full walkthrough (with success criteria and off-ramps), use the Quick Start guide.
For a given agent, choose one mode only. If you switch that agent to CLI mode, remove its old direct MCP configuration first.
Use one local runtime across repositories and Git worktrees. After configuring an installed backend with mcp setup, the agent selects a checkout on each call:
1mcp inspect codegraph --project /absolute/checkout
For the session’s assigned checkout, omit --project; explicit overrides do not change that default. Follow Working Across Projects and Worktrees (中文) for setup, project sets, independent workers, optional preparation, and safe cleanup.
CLI mode is the primary workflow for agent-style sessions. It keeps MCP as the backend protocol but narrows what the agent sees at each step:
instructions explains the current runtime and recommended flowinspect lets the agent discover only the server or tool it needsrun executes one selected tool after schema inspectionThat gives agent loops a smaller working surface without giving up the unified runtime behind 1mcp serve.
Use 1mcp proxy when you want the broadest client compatibility without giving up project context.
It is the recommended fallback after CLI mode because it:
.1mcprcDirect stdio mode is not the recommended path. It is mainly useful for debugging because 1MCP startup is slower than a thin standalone stdio setup.
Direct MCP attachment is still supported for clients that want to talk to the aggregated runtime over streamable HTTP.
Examples:
{
"mcpServers": {
"1mcp": {
"url": "http://127.0.0.1:3050/mcp?app=cursor"
}
}
}
claude mcp add -t http 1mcp "http://127.0.0.1:3050/mcp?app=claude-code"
Use this path if your client already speaks MCP natively, can work without project context, and you do not want CLI mode. For Codex, Claude, Cursor, and similar agent loops, prefer CLI mode first and proxy second.
Use the deeper docs if you are configuring or deploying the runtime itself:
flowchart LR
A[User or Agent] --> B[1mcp serve]
B --> C[Static servers loaded at startup]
B --> D[Template servers resolved from client or session context]
A --> E[CLI mode: instructions -> inspect -> run]
E --> B
F[Direct streamable HTTP client] --> B
G[stdio-compatible client] --> H[1mcp proxy]
H --> B
1MCP runs as an aggregated runtime behind 1mcp serve. Static servers are prepared from startup configuration, template servers are materialized when client context is known, and the runtime can use async loading for early HTTP listener availability and lazy loading for a stable tool surface. Instruction aggregation, presets, and notifications sit alongside that runtime rather than outside it.
Lazy loading is an opt-in stable tool-surface compatibility mode. It keeps the backend discovery and invocation surface at tool_list, tool_schema, and tool_invoke so capable agents can discover tools progressively without replacing their MCP tool table. Any explicitly enabled internal management tools remain directly exposed. Lazy loading reduces the initial schema payload, but it does not reduce backend connections or processes, make synchronous startup bind earlier, or repair orphaned proxy processes. See #392 for the async late-server visibility contract.
serve process1mcp instructions, 1mcp inspect <server>, 1mcp inspect <server>/<tool>, and 1mcp run <server>/<tool> --args '<json>'proxy for maximum compatibility with project context and template-server supportContributions are welcome. See CONTRIBUTING.md for the development workflow and LICENSE for the Apache 2.0 license.
One MCP server to aggregate them all - A unified Model Context Protocol server implementation
{ "mcpServers": { "1mcp-agent": { "command": "npx", "args": [ "-y", "@1mcp/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@1mcp/agent roda localmente via stdio.
Última verificação: 2026-11-16. One MCP server to aggregate them all - A unified Model Context Protocol server implementation