hyper-mcp MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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)

Démo en direct

Aperçu en pratique

hyper.replay ▶ prêt

0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

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

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

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

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

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : hyper-mcp

How to ship internal MCP tools securely with hyper-mcp

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

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

Prérequis

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

Déroulement

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.✓ Copié

→ 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.✓ Copié

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

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

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

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

Pièges

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

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

Déroulement

Load a new version

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

→ Plugin v2 shows in list_plugins
Unload old version if needed

Call hyper_mcp-unload_plugin on my-plugin:v1.✓ Copié

→ Only v2 remains

Résultat : A tight inner loop for plugin development.

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

hyper + mcptools

Debug plugin tool surface before Claude sees it

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

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
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

Coût et limites

Coût d'exécution

Quota d'API: None — local host
Tokens par appel: Depends on plugin — typically 100–1000
Monétaire: Free; OCI registry hosting may cost if private
Astuce: Share a single hyper-mcp host across clients instead of running many npm-based MCPs

Sécurité

Permissions, secrets, portée

Stockage des identifiants : Plugin secrets injected via config; OCI registry creds via standard docker/ghcr login

Sortie de données : Only to hosts listed in each plugin's allowed_hosts

Ne jamais accorder : unrestricted filesystem unrestricted network

Dépannage

Erreurs courantes et correctifs

Plugin fails signature verification

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

Vérifier : 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

Vérifier : 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

Alternatives

hyper-mcp vs autres

Alternative	Quand l'utiliser	Compromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills