MCP Dev Summit Mumbai 2026

Single agents calling MCP tools is a solved problem. Multi-agent swarms, where several agents coordinate on the same task, isn't.

The moment you go from one agent to three, you hit a set of problems that MCP itself doesn't solve and that most orchestration frameworks only paper over: how do agents share state without drowning each other in JSON, how do you isolate their execution when they're all touching the same files, and how does one agent pick up where another left off?

This talk walks through those three problems using a concrete example: a code review swarm. Three specialized reviewer agents (style, security, test coverage) work on the same PR in parallel. A fourth, a developer agent, reads their findings and applies the fixes. Each agent runs in its own isolated sandbox. They collaborate through a shared filesystem rather than by passing context in prompts.

This is a technical deep dive covering:
- why traditional file storage mechanisms are not optimized for agentic workloads
- why shared workspaces are better than passing state through prompts or RAG lookups
- why isolation boundaries are important when agents execute code

Includes live demo of swarm.