Main
Use CLI mode to reduce tool-surface overload: follow
instructions -> inspect -> runinstead of loading everything upfront.Centralize policy: keep auth, filtering, and presets in one runtime rather than duplicating per-client configs.
Pick one mode per agent session (CLI first, proxy second) and remove old direct wiring to avoid duplicates.
Source-backed notes
- README quick start shows:
npm install -g @1mcp/agent, then1mcp mcp add ..., then1mcp serve. - README documents the progressive discovery workflow:
1mcp instructions,1mcp inspect, then1mcp run ... --args '<json>'. - README includes examples for streamable HTTP attachment (
http://127.0.0.1:3050/mcp?app=...).
FAQ
- Do I have to migrate every client config now?: No — start with one runtime and migrate clients gradually once stable.
- Is CLI mode only for humans?: No — README targets agent users; the flow is designed for tool-using agents too.
- What’s the safest rollout?: Start with one upstream server + one agent, then expand inventory with review.