hyper-mcp MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Rust host + WASM plugin architecture — memory safe by construction
Plugins distributed as signed OCI artifacts (ghcr.io, Docker Hub)
Dynamic load/unload of plugins at runtime without restart
Fine-grained capability grants (network, filesystem, memory)

Live-Demo

In der Praxis

hyper.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "hyper": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/hyper-mcp-rs/hyper-mcp"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "hyper": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/hyper-mcp-rs/hyper-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "hyper": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/hyper-mcp-rs/hyper-mcp"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "hyper": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/hyper-mcp-rs/hyper-mcp"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "hyper",
      "command": "TODO",
      "args": [
        "See README: https://github.com/hyper-mcp-rs/hyper-mcp"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "hyper": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/hyper-mcp-rs/hyper-mcp"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add hyper -- TODO 'See README: https://github.com/hyper-mcp-rs/hyper-mcp'

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: hyper-mcp

How to ship internal MCP tools securely with hyper-mcp

👤 Platform teams building internal agent tools ⏱ ~45 min advanced

Wann einsetzen: You need to give engineers a curated toolset and can't trust them to vet every npm MCP package.

Voraussetzungen

hyper-mcp binary installed — Download release from github.com/hyper-mcp-rs/hyper-mcp/releases
An OCI registry to host plugins — GHCR or a private Harbor/ECR

Ablauf

Publish a signed plugin

I've built a WASM plugin at ./my-plugin.wasm. Push it to ghcr.io/acme/my-plugin:v1 and sign with sigstore.✓ Kopiert

→ Plugin available on registry with signature
Configure hyper-mcp to pull and verify it

Edit ~/.config/hyper-mcp/config.json to add the plugin URL with required signer identity.✓ Kopiert

→ Plugin appears in hyper_mcp-list_plugins after restart
Call the tool from Claude

Use the tool exposed by my-plugin to do <X>.✓ Kopiert

→ Tool runs sandboxed; attempts to exceed granted capabilities are denied

Ergebnis: A locked-down internal toolbelt where every plugin is signed, versioned, and sandboxed.

Fallstricke

Granting network access to all plugins by default — Configure per-plugin allowed_hosts; deny-by-default
Plugin signed by the wrong identity — hyper-mcp will reject — check sigstore/rekor logs for signer mismatch

Hot-swap agent tools with hyper-mcp without restarting the client

👤 Agent developers iterating on tool APIs ⏱ ~10 min intermediate

Wann einsetzen: You're testing a tool and want to iterate without killing the MCP session every 30 seconds.

Ablauf

Load a new version

Call hyper_mcp-load_plugin with the URL of my-plugin:v2. Confirm it loaded.✓ Kopiert

→ Plugin v2 shows in list_plugins
Unload old version if needed

Call hyper_mcp-unload_plugin on my-plugin:v1.✓ Kopiert

→ Only v2 remains

Ergebnis: A tight inner loop for plugin development.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

hyper + claude-code

Run hyper-mcp as the only MCP host inside Claude Code and route all custom tools through it

Replace my 5 npx-based MCPs with hyper-mcp pointing at my internal plugin registry.✓ Kopiert

hyper + mcptools

Debug plugin tool surface before Claude sees it

Use mcp tools to enumerate what hyper-mcp currently advertises.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
hyper_mcp-list_plugins		Inspect what's loaded; debug missing tools	0
hyper_mcp-load_plugin	url: str (oci://...), name?: str	Add a plugin at runtime	one OCI pull
hyper_mcp-unload_plugin	name: str	Remove a plugin — release memory and revoke its tools	0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None — local host
Tokens pro Aufruf: Depends on plugin — typically 100–1000
Kosten in €: Free; OCI registry hosting may cost if private
Tipp: Share a single hyper-mcp host across clients instead of running many npm-based MCPs

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: Plugin secrets injected via config; OCI registry creds via standard docker/ghcr login

Datenabfluss: Only to hosts listed in each plugin's allowed_hosts

Niemals gewähren: unrestricted filesystem unrestricted network

Fehlerbehebung

Häufige Fehler und Lösungen

Plugin fails signature verification

Check the sigstore signer identity matches config. Re-sign with cosign sign using the correct identity

Prüfen: cosign verify <oci-url>

Plugin loads but tool not visible to Claude

Claude caches the tool list at session start — restart the MCP client after loading

Prüfen: hyper_mcp-list_plugins shows the plugin and its advertised tools

WASM execution trap / panic

Plugin exceeded a resource limit or hit an unsafe op. Check logs; raise limit in config only if trusted

Alternativen

hyper-mcp vs. andere

Alternative	Wann stattdessen	Kompromiss
Arcade	You want a Python framework instead of WASM plugins	Less isolation; Python runtime instead of sandboxed WASM
Golf	Python-first, auto-discovery of tool files	Not plugin-isolated; all tools run in one process
FastMCP	Simple Python MCP, no registry/sandbox needs	No distribution story; you redeploy the whole server for each change

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen