https://opensource.microsoft.com/blog/2025/08/06/introducing-wassette-webassembly-based-tools-for-ai-agents/ for those who like their components in AI.
Something we don't call out in the article, but I'm sure folks here might appreciate: there is nothing MCP-specific to components loaded into Wassette. Wassette knows how to translate WIT to JSON Schema, which means it's able to ingest and serve arbitrary components!
For example, here is the WIT interface for our Rust fetch example:
package component:fetch-rs;
/// An example world for the component to target.
world fetch {
export fetch: func(url: string) -> result<string, string>;
}
With Wassette we're able to front this using MCP. But there's nothing stopping anyone from exposing this using any other protocol, or linking to it from other components. Which imo is the right way to approach this.
Last updated: Dec 06 2025 at 05:03 UTC