A production MCP pattern hides multi-agent orchestration behind a single thick tool
anilkr84 · reddit · 2026-07-26
Moving orchestration into the MCP server hides a multi-agent system behind one tool
The author describes a production pattern for MCP-based systems: instead of making the client LLM orchestrate a long chain of tools, move the reasoning and routing into the server and expose only one thick tool such as askagent(goal).
The three MCP generations
- Gen 1: thin stateless tools; the client handles all planning and state.
- Gen 2: tool plus skillpack; instructions improve usage, but orchestration still lives in the client.
- Gen 3: server-side orchestration; one call in, one answer out, with intermediate state kept on the server.
What this fixes
- Token cost stays flatter as tasks get deeper.
- Less goal drift, because the client only holds the question and answer.
- Smaller schema overhead.
- Routing can be handled by a domain-specific brain that adapts at runtime.
- The same tool can work across Claude, ChatGPT, or Codex.
Tradeoffs
- Higher latency per call.
- Less transparency and mid-chain steering.
- You are effectively running an agent system in production, so evals and observability become mandatory.
The author says their practical setup is a hybrid: one thick reasoning tool plus a few thin control tools for simple list/select operations.
More from coding & agent
- Vibe coding user asks whether ChatGPT or Codex is now the better default stack — yungcontent · 2026-07-26
- A voice-tech test app becomes a customizable agent expression template — sull · 2026-07-26
- Codex is fully open source and can run on any open-weights model — reach_vb · 2026-07-26
- fable-advisor switches to Opus 5 as its long-horizon agent orchestrator — daniel_mac8 · 2026-07-26
- Databricks AI data engineering boot camp goes free on YouTube August 3 — Zachly · 2026-07-26
- Working with code through agents can leave your mental model feeling blurry — round · 2026-07-26