The goal wasn’t a production-ready framework, just a POC to answer: how hard is it to add WASM to MCP, really? Turns out: not that hard.
I’m skeptical of one-vendor-controls-all MCP tool marketplaces (e.g., Composio/Pipedream). An open, contribution-driven model (think GitHub Actions) feels like a much better fit for Rust + MCP.
WASM brings sandboxing, safer untrusted code execution, and easy binary sharing — and runtimes like WasmEdge [2] make things like DB or network access much more realistic.
Overall, pretty happy with how it turned out. Happy to hear any feedback. Also curious what other Rust folks think about MCP + WASM as a direction.
- [1] https://github.com/ra0x3/mcpkit-rs - [2] https://wasmedge.org/