A team of agents, not one super-agent
Why multiple agents?
Two main reasons: parallelisation (independent tasks run simultaneously) and reusability (a design agent can serve both the marketing team and the product team). Debugging is also easier — you fix one specialised agent instead of untangling a monolithic system.
The smart home example
Climate control, lighting, security, energy management, grocery tracking, and an orchestrator. The security agent determines who enters and sets permissions. The climate agent reads weather APIs and controls temperature. The orchestrator routes user requests to the right specialist.
Agent communication
Agents communicate with each other using the same protocols they use with tools — including MCP. The climate agent might ask the energy agent about current usage before adjusting the thermostat. Each agent is treated like a tool by the others.
Hierarchy and orchestration
Most multi-agent systems have a hierarchy. The orchestrator agent handles user communication and delegates to specialists. Some systems allow all-to-all communication between certain agents (like climate and energy) while keeping others isolated. The structure depends on the task.
Think about a hospital. Which departments could be handled by specialised AI agents, and which ones would need to share information with each other?