MCP Dev Summit Bengaluru 2026

This is not just about Admiral Group PLC but for every organisation, tool schemas in MCP evolve as platforms change parameters get renamed, new required fields are added, response shapes shift. Agents built against an older schema break silently, produce incorrect results, or enter undefined behavior, and there is no established SemVer discipline for MCP tools today. This session proposes a practical versioning specification for MCP tool definitions covering additive-only change policies, explicit deprecation signals embedded in tool metadata, capability negotiation via request headers, and client-side schema compatibility layers. The session demonstrates these patterns with a real Kubernetes tool server that ships v1 and v2 tool definitions side by side, with running agents targeting each version independently, and a live migration showing how a breaking change is introduced and absorbed without downtime.