Runs and manages MCP servers in isolated containers with enterprise-grade security, observability, and Kubernetes integration.
Also known as stacklok/toolhive
- Stars
- 2,341
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 14, 2026
- License
- Apache-2.0
What is ToolHive MCP?
ToolHive runs and manages MCP servers in isolated containers with enterprise-grade security, observability, and Kubernetes integration.
Summary generated from the project's README
About ToolHive MCP server
Running MCP servers in isolated containers is what ToolHive enables for developers, platform engineers, and enterprise teams. It provides a secure way to manage tool execution by wrapping every server in a container with minimal permissions, preventing local credential exposure. Users can connect their preferred AI clients like Claude Code, Cursor, or GitHub Copilot to these managed servers through a single command or click.
Platform teams can deploy and scale these servers using a Kubernetes operator or run them locally via Docker and Podman. The architecture includes a Gateway to centralize security policies and an identity provider integration for SSO. It also features a Registry Server to curate trusted catalogs and a Runtime that supports OpenTelemetry and Prometheus for monitoring. By using semantic tool search and an optimizer, the platform helps reduce token usage by up to 85% during client interactions.
What you can do with it
- 1Secure local tool executionA developer can run MCP servers in isolated containers to ensure no local credentials are exposed.
- 2Enterprise Kubernetes deploymentPlatform engineers can manage a fleet of MCP servers using a Kubernetes operator and existing infrastructure.
- 3Reducing AI token costsUsers can minimize their token consumption by using semantic tool search to filter descriptions.
- 4Self-hosted data controlEnterprises with strict compliance needs can host their own MCP registry and gateway to keep data private.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablestacklok/toolhive is public and reachablegithub.com/stacklok/toolhive ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/stacklok/toolhive ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubThe open source MCP platform trusted by developers and enterprises
Run any MCP server securely, instantly, anywhere.
ToolHive runs every MCP server in an isolated container, enforces identity and access policy per request when configured with an authentication source, and gives platform teams the observability they need to put MCP in production.
Why ToolHive?
Here are some of the more common use cases for ToolHive:
Quick links
- 📥 Downloads
- 📚 Documentation
- 🚀 Quickstart guides:
- 💬 Discord
- 🤝 Contributing
- Stacklok Enterprise
Core capabilities
ToolHive architecture: Gateway, Registry Server, and Runtime, accessible through ToolHive UI and the CLI
ToolHive is built on a modular architecture to streamline secure MCP server management and integration. Here's how the main components work.
🔌 Gateway
Define dedicated endpoints from which your teams can securely and efficiently access tools.
- Orchestrate multiple tools into a virtual MCP with a deterministic workflow engine
- Define access policies and network endpoints
- Centralize control of security policy, authentication, authorization, auditing, etc.
- Integrate with your IdP for SSO (OIDC/OAuth compatible)
- Customize and filter tools and descriptions to improve performance and reduce token usage
- Connect with local clients like Claude Desktop, Cursor, VS Code, and VS Code Server
📦 Registry Server
Curate a catalog of trusted servers your teams can quickly discover and deploy.
- Integrate with the official MCP registry
- Add custom MCP servers
- Group servers based on role or use case
- Manage your registry with an API-driven interface (or embed in existing workflows for seamless integration and governance)
- Verify provenance and sign servers with built-in security controls
- Preset configurations and permissions for a frictionless user experience
⚙️ Runtime
Deploy, run, and manage MCP servers locally or in a Kubernetes cluster with security guardrails.
- Deploy MCP servers in the cloud via Kubernetes for enterprise scalability
- Run MCP servers locally via Docker or Podman
- Proxy remote MCP servers securely for unified management
- Kubernetes Operator for fleet and resource management
- Leverage OpenTelemetry and Prometheus for monitoring and audit logging
💻 Interfaces
Choose the interface that best fits your workflow.
- Use ToolHive UI for a cross-platform desktop experience
- Use the ToolHive CLI for terminal workflows and automation
- Discover, configure, and run MCP servers
- Automatically connect managed MCP servers to compatible AI clients
How it works together
- Admins curate and organize MCP servers in the Registry, configuring access and policies.
- Users discover, configure, and run MCP servers through ToolHive UI or the CLI, and ToolHive orchestrates deployment and access.
- Runtime securely deploys and manages MCP servers across local and cloud environments, integrating seamlessly with existing SDLC workflows, exporting analytics, and enforcing fine-grained access control.
- Gateway handles all inbound traffic, secures context and credentials, optimizes tool selection, and applies organizational policies.
Flexible deployment
Desktop experience
Individual developers can get started in minutes with the desktop UI or CLI, then apply the same concepts in enterprise environments.
Key features:
- Run any MCP server from a container image, or build one dynamically from common package managers
- Manage encrypted secrets and control network isolation with simple, local tooling
- Test and validate MCP servers using built-in tools like the official MCP Inspector
- Optimize token usage and tool execution with the MCP Optimizer
Get started with the UI: Quickstart, How-to guides
Get started with the CLI: Quickstart, How-to guides, Command reference
MCP guides: learn how to run common MCP servers with ToolHive
Kubernetes Operator
Teams and organizations manage MCP servers and registries centrally using familiar Kubernetes workflows.
Key features:
- Custom Resource Definitions for MCP servers, registries, and other ToolHive components
- Secure execution with container-based isolation and multi-namespace support
- Automated service creation and discovery, with ingress integration for secure access
- Enterprise-grade security and observability: OIDC/OAuth SSO, secure token exchange, audit logging, OpenTelemetry, and Prometheus metrics
- Hybrid registry server: curate from upstream registries, dynamically register local MCP servers, or proxy trusted remote services
Get started: Quickstart, How-to guides, CRD reference, Example manifests
Hybrid
ToolHive's complete solution for teams and enterprises supports MCP servers across all environments: on developer machines, inside your Kubernetes clusters, or hosted externally by trusted SaaS providers.
End users and developers manage approved MCP servers through ToolHive UI or the CLI, from guided desktop workflows to terminal-based automation and testing.
Enterprise teams can also leverage ToolHive to integrate MCP servers into custom internal tools, agentic workflows, or chat-based interfaces, using the same runtime and access controls.
Contributing
We welcome contributions and feedback from the community!
If you have ideas, suggestions, or want to get involved, check out our contributing guide or open an issue. Join us in making ToolHive even better!
Contribute to the CLI, API, and Kubernetes Operator (this repo):
Contribute to the UI, registry, and docs:
- 💻 Desktop UI repository
- 📦 ToolHive registry server repository
- 🛠️ ToolHive's built-in registry
- 📚 Documentation repository
License
This project is licensed under the Apache 2.0 License.
ToolHive MCP questions
How does ToolHive ensure security when running MCP servers?
ToolHive runs every MCP server in an isolated container and can enforce identity and access policies per request when configured with an authentication source.
Can I run ToolHive on my own infrastructure?
Yes, ToolHive allows you to self-host your MCP registry and gateway, making it suitable for enterprises with strict compliance requirements.
Does ToolHive support Kubernetes?
Yes, ToolHive includes a Kubernetes operator that allows platform engineers to deploy and manage MCP servers using familiar Kubernetes patterns and tools.
How can I connect my AI client to ToolHive?
You can connect clients like Claude Code, Cursor, or GitHub Copilot to MCP servers through ToolHive with a single click or command.