hyper-mcp MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

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)

라이브 데모

실제 사용 모습

hyper.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/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
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

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

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

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

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

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

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

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

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

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

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

context_servers에 추가. 저장 시 Zed가 핫 리로드.

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

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: hyper-mcp

How to ship internal MCP tools securely with hyper-mcp

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

언제 쓸까: You need to give engineers a curated toolset and can't trust them to vet every npm MCP package.

사전 조건

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

흐름

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.✓ 복사됨

→ 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.✓ 복사됨

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

Use the tool exposed by my-plugin to do <X>.✓ 복사됨

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

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

함정

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

언제 쓸까: You're testing a tool and want to iterate without killing the MCP session every 30 seconds.

흐름

Load a new version

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

→ Plugin v2 shows in list_plugins
Unload old version if needed

Call hyper_mcp-unload_plugin on my-plugin:v1.✓ 복사됨

→ Only v2 remains

결과: A tight inner loop for plugin development.

조합

다른 MCP와 조합해 10배 효율

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.✓ 복사됨

hyper + mcptools

Debug plugin tool surface before Claude sees it

Use mcp tools to enumerate what hyper-mcp currently advertises.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
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

비용 및 제한

운영 비용

API 쿼터: None — local host
호출당 토큰: Depends on plugin — typically 100–1000
금액: Free; OCI registry hosting may cost if private
팁: Share a single hyper-mcp host across clients instead of running many npm-based MCPs

보안

권한, 시크릿, 파급범위

자격 증명 저장: Plugin secrets injected via config; OCI registry creds via standard docker/ghcr login

데이터 외부 송신: Only to hosts listed in each plugin's allowed_hosts

절대 부여 금지: unrestricted filesystem unrestricted network

문제 해결

자주 발생하는 오류와 해결

Plugin fails signature verification

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

확인: 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

확인: 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

대안

hyper-mcp 다른 것과 비교

대안	언제 쓰나	단점/장점
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

hyper-mcp