2 ms·

I built hyper-mcp[1] as side project with each MCP as a WASM plugin. The idea is each plugin runs in their own wasm vm with limited network/file system access.

I built hyper-mcp[1] as side project with each MCP as a WASM plugin. The idea is each plugin runs in their own wasm vm with limited network/file system access. Plugins are written in any language, as long as they can compile to WASM and publish to OCI registry (signed & verified with sigstore) Recently, Microsoft released their own version of hyper-mcp named Wassete[2] Ideally, I want to make it like a gateway with more security & governance features in this layer. [1]: https://github.com/tuananh/hyper-mcp https://github.com/tuananh/hyper-mcp [2]: https://github.com/microsoft/wassette https://github.com/microsoft/wassette

fullstackwife 1y ago
For many years we were fine with running DLLs, Java .class deps, npm modules, brew packages etc. why do you think we need so much isolation for left-pad class mcp tools?
pmig 1y ago
Interesting we also just released our mcp gateway project under the name Hypr MCP[1]. [1]: https://github.com/hyprmcp/mcp-gateway https://github.com/hyprmcp/mcp-gateway
- tuananh 1y ago
  Cool. I want to add dynamic client registration but haven't got around to do it yet.
  - pmig 1y ago
    Feel free to just include our gateway in your docker compose file.