Our take
Activeregular commits and releases- Activity
- 76
- Community
- 68
- Issues
- 46
- Pull requests
- 80
+11 stars in the last 30 days
- Merges more pull requests than 88% of the projects we track
Wassette is an actively developed, promising approach to sandboxed MCP tools, but its early-development warning and limited recent issue closure make production adoption premature without your own validation.
Good fit if
- You want to experiment with WebAssembly Components as tools for MCP clients.
- Your agent workflow uses one of the documented clients and you can accommodate the Rust-based runtime.
- You value an MIT-licensed project with regular commits and releases and contributions from multiple people.
Look elsewhere if
- You need a runtime the project declares production-ready.
- Your team needs confidence that a substantial share of reported issues is being closed promptly.
- Your tools cannot be packaged or run as WebAssembly Components.
All health signals
| Last commit | 2026-10-27 (4 days ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 13 (latest v0.8.1, 2026-10-19) |
| Contributors | 22 (top contributor: 30% of commits) |
| Issues closed, last 90 days | 1+ |
| Pull requests merged, last 90 days | 82 (typically merged in 0 days) |
| Project age | 16 months |
Checked on 2026-10-31 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
977Forks
80Change since Nov 17, 2026: 0 stars·+1 forks
Overview
Wassette is a Rust runtime built on the Wasmtime security sandbox that lets AI agents use WebAssembly Components through the Model Context Protocol (MCP). It addresses the need to add reusable tools to agents while isolating those tools from the host environment.
The project is aimed at developers configuring MCP clients such as GitHub Copilot, Claude Code, and Codex CLI. Installation options include Linux, macOS, Windows, Homebrew, Nix, and Docker; components can be loaded from OCI references. Wassette is explicitly in early development, so expect changes before relying on it in production.
Key Features
- Runs WebAssembly Components inside Wasmtime's security sandbox.
- Exposes component capabilities to MCP clients as agent tools.
- Loads components from OCI references, such as
oci://ghcr.io/microsoft/time-server-js:latest. - Supports MCP client setup for GitHub Copilot, Copilot CLI, Claude Code, and Codex CLI.
- Offers installation options for Linux, macOS, Windows, Homebrew, Nix, and Docker.
- Keeps components reusable beyond MCP, according to the project's design goals.
Use Cases
- Agent developers can add a narrowly scoped tool, such as a time service, without implementing the capability inside the agent.
- Teams using MCP-compatible coding agents can load WebAssembly tools into their existing client setup.
- Component authors can distribute reusable tools through OCI artifacts for agents to load.
- Security-conscious developers can evaluate sandboxed component execution as an alternative to running tools directly on the host.
What you need
Detected in the repository
- Rust (from Cargo.toml)
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
On Linux or macOS, install with:
curl -fsSL https://raw.githubusercontent.com/microsoft/wassette/main/scripts/install.sh | bash
See the README and installation guide for platform-specific setup and MCP client configuration.
Considerations
The README warns that Wassette is in early development, is not production-ready, and may change significantly. The project is active, with frequent commits and releases, and has 22 contributors without a single contributor dominating the work. However, only a small number of issues were closed in the measured recent period, so teams should assess whether its issue handling meets their needs. The runtime is written in Rust, and components must be available as WebAssembly Components; the README does not describe a non-WebAssembly tool path.
Found this useful?
Share it with someone who would like wassette.