# ToolHive

> Apache-2.0 MCP server runner + gateway — each server in its own container

**Category:** AI Agents  
**Pricing:** open-source  
**URL:** https://docs.stacklok.com/toolhive/  
**GitHub:** https://github.com/stacklok/toolhive  
**Added:** 2026-10-09

---

## The Hook

ToolHive runs MCP servers the boring, safe way: each server in its own container with least-privilege defaults, discovered from a registry and wired into your clients — from a desktop app, a CLI, or a Kubernetes operator.

## What's Good

Apache-2.0 (stacklok/toolhive), v0.51.4. Desktop app, `thv` CLI, and Kubernetes operator share one model: a curated registry, per-server containers, secret handling, and client auto-config. The operator adds declarative policy, IdP integration, and OpenTelemetry traces. Self-hostable registry and gateway for teams that cannot send MCP traffic through a SaaS. ★~2.3k.

## The Catch

Every MCP server runs in its own container, so you need Docker or Podman even on a laptop. Identity and access policies only apply once you connect an OIDC/OAuth provider — out of the box it is isolation, not authorization. Stacklok sells an enterprise tier on top. Vs metamcp (aggregator/proxy that merges servers into one endpoint) and contextforge (gateway/federation): ToolHive’s lane is per-server container isolation plus a registry.

## Verdict

Apache-2.0 container-isolated MCP runner when you want every server sandboxed and auditable — bring Docker/Podman and an IdP for real policy.