Installer wassette avec Homebrew, winget

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• wassette

Historique du projet

The project's changelog records v0.1.0 on August 5, 2025 as the initial Wassette release, adding the core MCP server, SSE and stdio transports, component lifecycle management, policy-based permissions, examples, CLI support, installation, and documentation.

Microsoft's open source blog introduced Wassette on August 6, 2025 through the Azure Core Upstream team. The announcement described it as a security-oriented runtime for running WebAssembly Components via MCP, able to fetch components from OCI registries and execute them with Wasmtime-backed sandboxing.

Historique d'adoption

As of its early public releases, Wassette is explicitly marked by its repository as early development and not production ready. Its adoption story is therefore mostly experimental: agent developers can wire it into MCP-capable clients such as GitHub Copilot, Cursor, Claude Code, and Gemini CLI, then load Wasm components as tools.

Its significance comes from timing. MCP made agent tools easy to connect, but also raised the risk of giving agents arbitrary local executables. Wassette's answer is to package tools as WebAssembly Components, inspect typed interfaces, and enforce a deny-by-default permission model before granting filesystem, network, or other host access.

Modes d'utilisation

Users register Wassette as an MCP server with an agent, then ask the agent to load a WebAssembly Component. Wassette translates the component's typed exports into MCP tools and brokers calls through a Wasmtime sandbox.

Component authors can build tools in languages that target the WebAssembly Component Model, publish them as OCI artifacts, and let Wassette fetch and run them. That makes it a package-oriented security layer for agent tools rather than a general-purpose Wasm CLI.

Pourquoi les passionnés de paquets s'y intéressent

Wassette is package-nerd interesting because it combines three packaging interfaces that usually live separately: MCP tool registration, OCI artifact distribution, and Wasm Component interfaces. It treats tool installation as something an agent may request dynamically, but tries to keep the runtime authority narrow and auditable.

For the WebAssembly ecosystem, it is a concrete example of the Component Model's promise: tools can expose typed functions instead of ad hoc JSON-over-process contracts, and the host can reason about permissions before executing untrusted code.

Chronologie

• 2025-08-05: Wassette v0.1.0 initial release added the core MCP server, component lifecycle management, and permission system.
• 2025-08-06: Microsoft Open Source introduced Wassette publicly as WebAssembly-based tools for AI agents.
• 2025-2026: Documentation and repository warnings continued to frame Wassette as early-stage, security-oriented infrastructure for MCP and WebAssembly Component experiments.

Related projects

• Wasmtime provides the underlying WebAssembly runtime sandbox.
• The WebAssembly Component Model and WIT provide the typed interfaces Wassette exposes as tools.
• The Model Context Protocol is the protocol surface through which AI agents call Wassette-managed tools.
• OCI registries are used as a distribution mechanism for WebAssembly Components.

Sources

• https://github.com/microsoft/wassette
• https://github.com/microsoft/wassette/blob/main/CHANGELOG.md
• https://microsoft.github.io/wassette/
• https://microsoft.github.io/wassette/latest/concepts.html
• https://opensource.microsoft.com/blog/2025/08/06/introducing-wassette-webassembly-based-tools-for-ai-agents/