MCP Dev Summit Bengaluru 2026

In 2013, shipping a Python service meant picking a base OS, writing an initscript, and fighting pip against the system package manager. Docker made it one command. Twelve years later, shipping an MCP server still feels pre-Docker — pick a language, spin up a process, hope the dependencies cooperate.

The WebAssembly Component Model quietly shipped the pieces it was missing in 2023. wasmcp, Microsoft Wassette, and Fermyon Spin now compose a single MCP server from Python tools that use pandas, TypeScript tools that use Zod, and Rust middleware that uses Regorus. One process. Hard isolation between components. One signed artifact, distributed through OCI registries, cold-starting in the low milliseconds.

This is a live-demo talk. I'll build a polyglot MCP server on stage, push it to a registry, and run the same bytes in four environments — a Kubernetes pod, a Spin function, a browser tab, and a Raspberry Pi. And I'll be honest about what WASM still can't do.