The night four MCP servers started acting like one system

Short summary

The author describes an agent workflow where four MCP servers—Agent Communication, Resource Sentinel, Agent Coordination, and Launcher Project Registry—coordinated to let Hermes hand a code review to a coding agent, request compute capacity, run Codex, and record durable task history. Each server owns a narrow domain and returns structured state, avoiding a monolithic orchestration function. The trace reveals real operational gaps (e.g., missing registry slugs) that durable state makes visible rather than hiding.

• •Four MCP servers coordinated sequentially: communication, resource admission, coordination, and project registry
• •Resource Sentinel admitted a 2.2GB/45-CPU-weight Codex job under a time-limited lease without running shell commands
• •Durable task history preserved submitted/working/completed events with artifact references and verification notes

Generated with AI, which can make mistakes.