Airsc is free for everyone. If it helps you, support it with $2–$20.

Support
PluginSafeDeploy & DevOpsAdvanced

hyper-mcp

hyper-mcp-rs · hyper-mcp-rs/hyper-mcp

A fast and secure MCP server that allows extending AI agent capabilities through WebAssembly plugins, working with Claude Desktop, Cursor, and other MCP-compatible apps.

📦️ A fast, secure MCP server that extends its capabilities through WebAssembly plugins.

881 stars66License: Apache-2.0Updated 12 days ago0 opens

Preview

▍

What you can do with it

  • Host custom AI agent tools securely on a self-managed MCP server.
  • Deploy WebAssembly-based agent plugins that can run on various platforms.
  • Integrate specialized functionalities into AI agents using a language compiled to WebAssembly.

Safety check

Safe

No risky patterns found in the files we scanned.

Automated scan of the repo files. Always review code you run.

From the README

hyper-mcp

A fast, secure MCP server that extends its capabilities through WebAssembly plugins.

What is it?

hyper-mcp makes it easy to add AI capabilities to your applications. It works with Claude Desktop, Cursor IDE, and other MCP-compatible apps. Write plugins in your favorite language, distribute them through container registries, and run them anywhere - from cloud to edge.

Features

  • Write plugins in any language that compiles to WebAssembly
  • Distribute plugins via standard OCI registries (like Docker Hub)
  • Built on Extism for rock-solid plugin support
  • Sanboxing with WASM: ability to limit network, filesystem, memory access
  • Lightweight enough for resource-constrained environments
  • Support stdio transport protocol
  • Deploy anywhere: serverless, edge, mobile, IoT devices
  • Cross-platform compatibility out of the box
  • Support tool name prefix to prevent tool names collision
  • Dynamic plugin loading and unloading (configurable)

Security

Built with security-first mindset:

  • Sandboxed plugins that can't access your system without permission
  • Memory-safe execution with resource limits
  • Secure plugin distribution through container registries
  • Fine-grained access control for host functions
  • OCI plugin images are signed at publish time and verified at load time with sigstore.

Installation

Prerequisites

cosign — required for loading plugins from OCI registries (oci:// URLs).

hyper-mcp verifies the cryptographic signature of every OCI plugin before loading it to ensure the plugin has not been tampered with and comes from a trusted source. This verification is performed by shelling out to the cosign CLI, which must be installed and available on your PATH.

Install cosign by following the official instructions: https://docs.sigstore.dev/cosign/system_config/installation/

Note: If you only use file://, http://, https://, or s3:// plugin URLs, cosign is not needed. You can also bypass signature verification for OCI plugins by setting insecure_skip_signature: true in your config or the HYPER_MCP_INSECURE_SKIP_SIGNATURE=true environment variable, but this is not recommended for production use.

Install from Homebrew

hyper-mcp is published on Homebrew for macOS and Linux in two places:

Homebrew core — no tap setup required:

brew install hyper-mcp

Our own tap (hyper-mcp-rs/tap) — bumped automatically on every GitHub Release, so it picks up new versions immediately:

brew install hyper-mcp-rs/tap/hyper-mcp

Both install the same binary. Prefer the core formula unless you want the absolute latest release the moment it ships.

Pre-built binaries (GitHub Releases)

Download the latest release for your platform from GitHub Releases:

Chose the version that you want and download the architecture-specific binary.

PlatformArchitectureDownload
macOSApple Silicon (ARM64)hyper-mcp-aarch64-apple-darwin.tar.gz
LinuxARM64hyper-mcp-aarch64-unknown-linux-gnu.tar.gz
Linuxx86_64hyper-mcp-x86_64-unknown-linux-gnu.tar.gz
Windowsx86_64hyper-mcp-x86_64-pc-windows-msvc.zip

macOS / Linux:

Donwload the .tar.gz file, extract it, and place hyper-mcp in /usr/local/bin.

Windows:

Download the .zip file, extract it, and place hyper-mcp.exe somewhere on your PATH.

Install from crates.io

If you have Rust installed, you can install hyper-mcp directly from crates.io:

cargo install hyper-mcp

Getting Started

  1. Create your config file:
    • Linux: $HOME/.config/hyper-mcp/config.json
    • Windows: {FOLDERID_RoamingAppData}\hyper-mcp\config.json. Eg: C:\Users\Alice\AppData\Roaming\hyper-mcp\config.json
    • macOS: $HOME/Library/Application Support/hyper-mcp/config.json
{
  "plugins": {
    "time": {
      "url": "oci://ghcr.io/hyper-mcp-rs/time-plugin:latest",
      "description": "Get current time and do time calculations"
    },
    "qr_code": {
      "url": "oci://ghcr.io/hyper-mcp-rs/qrcode-plugin:latest",
      "description": "Generate QR codes from text"
    },
    "hash": {
      "url": "oci://ghcr.io/hyper-mcp-rs/hash-plugin:latest"
    },
    "myip": {
      "url": "oci://ghcr.io/hyper-mcp-rs/myip-plugin:latest",
      "description": "Get your current public IP address",
      "runtime_config": {
        "allowed_hosts": ["1.1.1.1"]
      }
    },
    "fetch": {
      "url": "oci://ghcr.io/hyper-mcp-rs/fetch-plugin:latest",
      "runtime_config": {
        "allowed_hosts": ["*"],
        "memory_limit": "100 MB",
      }
    }
  }
}

📖 For detailed configuration options including authentication setup, runtime configuration, and advanced features, see RUNTIME_CONFIG.md

Supported URL schemes:

  • oci:// - for OCI-compliant registries (like Docker Hub, GitHub Container Registry, etc.). Requires cosign for signature verification (see Prerequisites)
  • file:// - for local files
  • http:// or https:// - for remote files
  • s3:// - for Amazon S3 objects (requires that you have your AWS credentials set up in the environment)
  1. Start the server:
$ hyper-mcp
  • Uses stdio transport protocol.
  • If you want to debug, use RUST_LOG=debug.
  • If you're loading unsigned OCI plugin, you need to set insecure_skip_signature flag or env var HYPER_MCP_INSECURE_SKIP_SIGNATURE to true

Running in SSE/streamable-http: To do this, wrap hyper-mcp in one of the many proxies that supports the network transports AND that creates an instance of hyper-mcp per client connection.

Output Logging

hyper-mcp automatically logs all output to daily ro

View source on GitHub