• Convenience: Wassette makes it easy to extend AI agents with new tools, all without ever having to leave the chat window.
• Reusability: Wasm Components built for Wassette are generic and reusable; there is nothing MCP-specific about them.
• Security: Wassette is built on the Wasmtime security sandbox, providing browser-grade isolation of tools.

For Linux and macOS, you can install Wassette using the provided install script:

curl -fsSL https://raw.githubusercontent.com/microsoft/wassette/main/install.sh | bash

This will detect your platform and install the latest wassette binary to your $PATH.

We also provide a Homebrew formula for macOS and Linux.

For Windows, you can download the latest release from the GitHub Releases page

With Wassette installed, the next step is to register it with your agent of choice. We have a complete complete setup guide for all agents here, including Cursor, Claude Code, and Gemini CLI. However to get started with Visual Studio Code, just run the following command:

code --add-mcp '{"name":"Wassette","command":"wassette","args":["serve","--stdio"]}'

Now that your agent knows about Wassette, we are ready to load Wasm Components. To teach your agent to tell the time, we can ask it to load a time component:

Please load the time component from oci://ghcr.io/yoshuawuyts/time:latest

Now that the time component is loaded, we can ask your agent to tell you the current time:

What is the current time?

The agent will respond with the current time, which is fetched from the time component running in a secure WebAssembly sandbox:

The current time July 31, 2025 at 10:30 AM UTC

Congratulations! You've just run your first Wasm Component and taught your agent how to tell time!

Wasm Components provide fully typed interfaces defined using WebAssembly Interface Types (WIT). Wassette can take any Wasm Component and load it as an MCP tool by inspecting the types it exposes. Take for example the following WIT definition for a time server:

package local:time-server;

world time-server {
    export get-current-time: func() -> string;
}

You'll notice that this interface doesn't mention MCP at all; it is just a regular library interface that exports a function. That means there is no such thing as a "Wassette-specific Wasm Component". Wassette is able to load any Wasm Component and expose its functions as MCP tools. Just like Components built for Wassette can be re-used by other Wasm runtimes.

See the examples/ directory for a complete list of examples. Here is a selection of examples written in different languages:

You can join us via the #wassette channel on the Microsoft Open Source Discord:

Please see CONTRIBUTING.md for more information on how to contribute to this project.

This project is licensed under the MIT License.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.