OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Hyper MCP

Hyper MCP is a Rust MCP server that exposes capabilities to MCP-compatible applications through WebAssembly plugins. It supports stdio transport, configurable plugin sources and runtime settings.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Hyper MCP — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Hyper MCP when an MCP-compatible application needs capabilities provided by configurable WebAssembly plugins, and stdio suits the connection or a compatible proxy can provide the required network transport.

Who it is for

  • Developers integrating modular tools or application-specific capabilities into MCP-compatible apps.
  • Teams building or operating MCP services that need plugins compiled to WebAssembly.
  • Plugin authors who want to distribute WebAssembly modules through OCI registries or other supported sources.

Documented uses

  • Expose plugin-provided functions such as time calculations, QR-code generation, hashing, public-IP lookup or fetching to an MCP client.
  • Configure plugin locations and runtime settings in a JSON file.
  • Load plugins from OCI registries, local files, HTTP(S) sources or S3 objects.
Before you choose

Requirements & limits

  • The documented built-in transport is stdio; network transports require a proxy that creates an instance per client connection.
  • OCI plugin sources require the cosign CLI for signature verification.
  • Plugin code can be written in any language that compiles to WebAssembly.
  • The repository identifies Rust as the server language and Apache-2.0 as its license.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Configure plugins and start Hyper MCP over stdio

Create a plugin configuration and start the server using its documented stdio transport.

Before you start

  • Hyper MCP installed using a documented installation method.
  • A plugin configuration file at the documented path for the operating system.
  • cosign installed and on PATH when loading plugins from OCI registries.
  • AWS credentials available in the environment when loading plugins from S3.

Steps

  1. Create config.json in the documented user configuration directory for Linux, Windows or macOS.

  2. Add plugin entries under the plugins key, including each plugin's URL and optional description or runtime_config.

  3. Choose a supported URL scheme: oci://, file://, http://, https:// or s3://.

  4. Run hyper-mcp; it uses stdio transport.

Expected outcome

The server starts with the plugins listed in the configuration and communicates over stdio.

Guide limitations

  • OCI plugin loading requires cosign for signature verification; bypassing verification is documented but not recommended for production.
  • S3 plugin URLs require AWS credentials in the environment.
  • SSE and streamable HTTP require a compatible proxy that creates a server instance per client connection.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
12 October 2026
Original website title
hyper-mcp-rs/hyper-mcp · Official homepage title · retained in its source language
How we review sourcesSuggest a correction