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.
Here are some of the more common use cases for ToolHive:
| Developers. Run MCP servers with more security and more (token) savings | Platform Engineers. Run MCP on your existing Kubernetes infrastructure | Enterprises. Self-host MCP servers and stay in control of your data |
| Connect Claude Code, Cursor, GitHub Copilot, or your preferred client to MCP servers with a single click or command. ToolHive wraps every MCP server in an isolated container with a minimal permission file (no local credentials) and uses semantic tool search to reduce your token usage by up to 85%. |
Put an end to shadow MCP use by your developers, and give your security team the audit logs and configurable identity enforcement they require. ToolHive includes a Kubernetes operator, so you can declare policies, integrate with your IdP and observability stack, emit OTel traces, and more … all with familiar tools and patterns. |
Most MCP solutions are SaaS, but your compliance requirements prohibit sensitive info from being processed by SaaS providers. ToolHive is the exception that allows you to self-host your MCP registry, gateway, etc. You can pilot the entire platform, and when you’re ready to scale, Stacklok’s got the added capabilities and expert team ready! |
| Download ToolHive and get started | Explore the Kubernetes operator in our docs Read more about running MCP on Kubernetes |
Learn more about Stacklok’s platform Compare open source ToolHive and Stacklok Enterprise |
- 📥 Downloads
- 📚 Documentation
- 🚀 Quickstart guides:
- 💬 Discord
- 🤝 Contributing
Stacklok Enterprise
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.
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
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
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
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
- 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.
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
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
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.
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: |
|
This project is licensed under the Apache 2.0 License.