hyper

hyper-mcp is a fast, secure MCP server written in Rust that hosts WebAssembly plugins to extend its capabilities. It exposes an OCI-plugin model, allowing plugins to be distributed via container registries and loaded at runtime. The server communicates with clients over the stdio transport protocol and supports per-plugin runtime configuration, memory and I/O sandboxing, and fine-grained access controls. To get started, run the hyper-mcp binary; the server will load configured plugins and expose their capabilities to MCP-compatible clients such as Claude Desktop or Cursor IDE. Tools and plugins can be added by listing their OCI URLs in a local config file. The project ships with a collection of example plugins (time, qrcode, hash, myip, fetch, etc.) to help you experiment with standard plugin interfaces. You can also configure logging and debugging via environment variables to tailor observability during development and deployment.

Prerequisites:

• Rust toolchain (Rustup, cargo)
• Access to the internet to fetch dependencies

1. Install Rust (if not already installed):

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

2. Clone the repository and build the binary:

git clone https://github.com/hyper-mcp-rs/hyper-mcp.git
cd hyper-mcp

# Build a release binary
cargo build --release

3. Run the server:

./target/release/hyper-mcp

4. Optional: set up a project-local configuration and run in a scoped environment:

# Example config at $HOME/.config/hyper-mcp/config.json
{
  "plugins": {
    "time": { "url": "oci://ghcr.io/hyper-mcp-rs/time-plugin:latest" }
  }
}

5. If you prefer to run from a prebuilt binary or via a package manager, refer to the project’s release assets and install instructions for your platform.

Notes:

• Use RUST_LOG to control log verbosity (e.g., RUST_LOG=debug hyper-mcp).
• For unsigned OCI plugins, you may need to enable insecure signature checks by setting HYPER_MCP_INSECURE_SKIP_SIGNATURE=true or passing the corresponding flag in config.
• Logs are written to daily rolling files by default; you can override the log path with HYPER_MCP_LOG_PATH.
• Plugins are loaded from OCI registries or local files using URL schemes such as oci://, file://, http(s)://, or s3://. Ensure network access and proper authentication as required by your registry.
• The server uses stdio transport by default; to support streaming or multi-client scenarios, consider wrapping hyper-mcp with a proxy that can create per-client instances.