ToolHive: The open-source way to run any MCP server securely
Stacklok's open-source ToolHive runs Model Context Protocol servers in isolated containers with per-request identity enforcement, audit logging and a signed registry.
ToolHive, shipped under Apache 2.0, containersizes MCP servers locally via Docker or Podman or in clusters through a Kubernetes operator, applying permissions, network filtering, and secrets management. The platform includes a Registry Server implementing the official MCP Registry API with signing and provenance verification, a Virtual MCP Server gateway with OIDC/OAuth single sign-on and OpenTelemetry traces, and a desktop Portal for one-click installs. The browser-based cloud UI is retired, so the desktop app and CLI are the supported rollout paths.
- Runs MCP servers in per-container isolation with minimal permissions and no local credentials
- Registry Server signs and verifies provenance via the official MCP Registry API
- Gateway unifies backends behind one endpoint with OIDC/OAuth SSO and OpenTelemetry
- Browser cloud UI retired; build on desktop app and CLI
- Products
- ToolHiveModel Context Protocol
From the original article
2 min read at helpnetsecurity.com
ToolHive is an open-source platform that runs Model Context Protocol servers inside containers. An MCP server is the connector that lets an AI client like Cursor or Claude Code reach an outside tool, and Stacklok ships ToolHive under Apache 2. 0, so the runtime, the Kubernetes operator, and the registry cost nothing to self-host.
By @helpnetsecurity · helpnetsecurity.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.