toolhive MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Container-isolated MCP servers (Docker / Kubernetes)
Curated, verified MCP registry with preset configs
One-click install into Claude Desktop, Cursor, VS Code
SSO, encrypted secrets, audit logging, OpenTelemetry
Desktop app, web, CLI, and Kubernetes Operator

라이브 데모

실제 사용 모습

toolhive.replay ▶ 준비됨

0/0

설치

클라이언트 선택

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

{
  "mcpServers": {
    "toolhive": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/stacklok/toolhive"
      ],
      "_inferred": true
    }
  }
}

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

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

{
  "mcpServers": {
    "toolhive": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/stacklok/toolhive"
      ],
      "_inferred": true
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "toolhive": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/stacklok/toolhive"
      ],
      "_inferred": true
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "toolhive": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/stacklok/toolhive"
      ],
      "_inferred": true
    }
  }
}

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

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "toolhive",
      "command": "TODO",
      "args": [
        "See README: https://github.com/stacklok/toolhive"
      ]
    }
  ]
}

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

~/.config/zed/settings.json

{
  "context_servers": {
    "toolhive": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/stacklok/toolhive"
        ]
      }
    }
  }
}

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

claude mcp add toolhive -- TODO 'See README: https://github.com/stacklok/toolhive'

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

사용 사례

실전 활용법: toolhive

How to install a community MCP without trusting random `npx -y` scripts

👤 Security-conscious engineers ⏱ ~10 min beginner

언제 쓸까: You want the GitHub MCP running locally but don't want to give it unrestricted filesystem access.

사전 조건

Docker Desktop — docker.com
ToolHive desktop app — stacklok.com/download

흐름

Open ToolHive, search the registry

Install 'github' from the ToolHive registry.✓ 복사됨

→ Container pulled, config prompt for GITHUB_TOKEN
Auto-configure your client

Click 'Connect to Claude Desktop'.✓ 복사됨

→ Claude Desktop config updated; restart required
Verify isolation

Confirm the container only has the env vars you set and no host filesystem mounts.✓ 복사됨

→ Inspect container config in the ToolHive UI

결과: A sandboxed MCP with least-privilege access to your machine.

함정

Filesystem MCPs need a mount — default no-mount is too tight — Add a scoped mount (e.g. ~/Projects only) rather than full-home

How to deploy MCPs on Kubernetes for a platform team

👤 Platform engineers ⏱ ~60 min advanced

언제 쓸까: You want org-wide standardized MCP availability.

사전 조건

Kubernetes cluster + cluster-admin — Existing EKS/GKE/AKS or kind for dev
ToolHive Operator CRDs installed — kubectl apply -f the Stacklok-provided manifests

흐름

Declare MCPServer resources

kubectl apply -f mcp-github.yaml — declaratively register a GitHub MCP with scoped secrets.✓ 복사됨

→ Pod running; Portal lists it
Expose to users via Portal

Engineers log into the Portal with SSO and one-click install into their client.✓ 복사됨

→ Per-user configs auto-generated

결과: Central catalog + per-user install; auditable.

함정

Stdio MCPs don't fit network-exposed Kubernetes well — Prefer Streamable HTTP MCPs for k8s; use the gateway for stdio ones

How to produce an audit trail of all MCP tool calls

👤 Compliance, security teams ⏱ ~30 min intermediate

언제 쓸까: Your org needs 'who called what tool when' for SOC2 or internal policy.

흐름

Enable OpenTelemetry export

In ToolHive settings, set the OTLP endpoint to your collector.✓ 복사됨

→ Traces appear in your backend
Tag by user

Enable per-user identity propagation via SSO.✓ 복사됨

→ Each trace has actor id

결과: Per-user, per-tool audit log.

조합

다른 MCP와 조합해 10배 효율

toolhive + mcphub

Use ToolHive for isolation, MCPHub for multi-server routing

Run each MCP in its own ToolHive container and expose them through MCPHub groups.✓ 복사됨

toolhive + unla

Combine ToolHive-run MCPs with Unla's REST-to-MCP conversion

Register our Unla-converted internal API in ToolHive so it runs containerized with SSO.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
(platform) registry-install	mcp_name	Install a verified MCP	free
(platform) gateway-proxy	Transport + auth policy	Front your MCPs with policy	free
(platform) runtime-isolate	Container spec	Sandboxed execution	free + infra cost

비용 및 제한

운영 비용

API 쿼터: None at platform layer
호출당 토큰: Minimal overhead
금액: Desktop + CLI + open-source Operator are free. Enterprise plans for support/compliance.
팁: Start with the free tier; upgrade only if you need dedicated SLAs or advanced SSO/RBAC.

보안

권한, 시크릿, 파급범위

최소 스코프: Per-MCP: least privilege env vars and mounts SSO for team deployments

자격 증명 저장: Encrypted secrets manager built into ToolHive

데이터 외부 송신: Determined by downstream MCPs; ToolHive adds telemetry if configured

절대 부여 금지: Don't auto-grant filesystem mounts beyond what each MCP needs

Running too many MCPs in a single container defeats the isolation; one per container.

문제 해결

자주 발생하는 오류와 해결

Container starts then exits immediately

Check the MCP's required env vars are set (e.g., GITHUB_TOKEN). View logs in ToolHive UI.

Claude Desktop can't find the server after install

Restart Claude Desktop — config changes only load on launch.

K8s Operator CRD install fails

Ensure cluster-admin and supported k8s version (>= 1.27).

확인: kubectl version

OTLP traces missing

Collector endpoint must accept OTLP/HTTP or OTLP/gRPC; confirm protocol match.

대안

toolhive 다른 것과 비교

대안	언제 쓰나	단점/장점
MCPHub	You want multi-server aggregation more than container isolation	Not container-runtime focused
Docker MCP Toolkit	You prefer Docker's own integrated tooling	Less curated registry

toolhive

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

설치

클라이언트 선택

사용 사례

실전 활용법: toolhive

How to install a community MCP without trusting random `npx -y` scripts

사전 조건

흐름

함정

How to deploy MCPs on Kubernetes for a platform team

사전 조건

흐름

함정

How to produce an audit trail of all MCP tool calls

흐름

조합

다른 MCP와 조합해 10배 효율

도구

이 MCP가 노출하는 것

비용 및 제한

운영 비용

보안

권한, 시크릿, 파급범위

문제 해결

자주 발생하는 오류와 해결

대안

toolhive 다른 것과 비교

더 보기

리소스