Dev Tools · 18h ago
Four MCP servers orchestrate agent workflow without a central controller
An agent called Hermes used four small MCP servers to hand off a code review, request resources, and run Codex without overloading the local machine. The servers handled agent communication, resource admission, coordination, and project registry separately. The workflow recorded 18 passing tests and preserved a durable history of edge cases.
Meridian48 take
The real story is not the demo but the architectural choice to keep each MCP server narrowly scoped, avoiding the temptation to build one monolithic orchestration layer.
mcp-serversagent-orchestration