Skip to main content

Community Calls

Weekly wasmCloud Wednesday agendas, notes, and recordings. Add the next meeting to your Calendar or watch it live on YouTube.

wasmCloud v2 on Kubernetes: Runtime Operator, wash host & WASI P3

The November 5, 2025 wasmCloud community call is centered on WebAssembly on Kubernetes. Lucas Fontes demos the next generation of wasmCloud — wasmCloud v2 — bringing up a Kubernetes cluster, installing the runtime operator and a new wasmCloud host over NATS via Helm, and scheduling a workload onto one of three host groups using nothing but kubectl get host. The new wash host command turns the single wash binary into a cluster host, with all scheduling intelligence moved into the operator so you can bring your own scheduler — or even your own host. Bailey Hayes frames the road to v2.0.0-rc1, and Victor Adossi closes with an update on JCO standing up as a second reference implementation for WASI Preview 3.

openapi2mcp Wasm Plugin Demo, WASI P3 & JCO Async for the Component Model

The October 29, 2025 wasmCloud community call is a short, demo-led session focused on the Wasm component model and the tooling around it. Liam Randall demos the new openapi2mcp plugin for Wasm Shell, which turns an OpenAPI specification into a ready-to-run MCP server packaged as a WebAssembly component, then shows pushing it to Kubernetes and wiring it into Claude. Victor Adossi gives a WASI P3 update: the P3 feature set is essentially complete on the Rust side, and his JCO async work — transpiling P3 components to JavaScript for Node and the browser — is on track to become the second WASI P3 reference implementation.

wasmCP MCP Servers & Long-Running Services on the Wasm Component Model

The October 22, 2025 wasmCloud community call is a two-demo deep dive into the Wasm component model. Corey and Ian demo wasmCP, a framework for building Model Context Protocol (MCP) servers as composable WebAssembly components in Rust, Python, and TypeScript — scaffolding tools, chaining them through a transport-agnostic WIT-defined middleware pattern, and running the result on Wasmtime, wash, or Cosmonic Control. Brooks Townsend then introduces wasmCloud services: long-running components targeting the WASI CLI world that open the door to component-native capability providers.

wasmCloud Runtime Crate: Embedding Wasmtime & the Component Model

The October 15, 2025 wasmCloud community call dives into the Wasm component model through a new wasmCloud runtime crate. Brooks Townsend walks through the crate — an opinionated embedding of Wasmtime that auto-links components via workload resolution, adds host plugins for WASI and custom interfaces, and exposes a much-simplified host API. The conversation widens into how component instances are managed across requests, how that shapes WIT design, and the community's push toward common agentic protocols like MCP and ACP.

MCP Server as a Wasm Component: OpenAPI to MCP, JCO & Component Model

The October 8, 2025 wasmCloud community call shows off an MCP server as a Wasm component. Bailey Hayes builds a Model Context Protocol server from idiomatic TypeScript, generates its tools from an OpenAPI spec with a new wash plugin, and compiles the whole thing to a portable, sandboxed WebAssembly component via JCO and StarlingMonkey. Victor Adossi traces the road to running plain JavaScript and WASI Preview 3 components in Wasm, and Brooks Townsend lands the wasmCloud runtime crate into wash ahead of Q4 roadmap planning.