MCP Dev Summit Mumbai 2026

When we tried to scale our multi-agent MCP system beyond a single node, the orchestrator broke immediately.

Each model running on a different machine means the orchestrator had to track which models it called, which responses arrived, and which were pending. The moment the orchestrator restarted, everything was gone. Models got called twice. Responses were lost. Consensus became inconsistent.

Turns out this is the sticky session problem. And the ecosystem is still figuring it out.

As SEP-1442 is moving MCP toward a stateless-by-default transport model. But most deployments still depend on session affinity. When you are orchestrating models across distributed nodes, that dependency breaks everything.

This talk covers what we learned designing around it:

- Why multi-agent MCP orchestration creates hidden session dependencies
- How to decouple consensus state from the orchestrator process using structured event logs
- Migration patterns that preserve workflow correctness without session affinity
- Stateless MCP is not just an infrastructure concern. It is what makes multi-agent consensus reliable at scale.