stacklok/toolhive

[![Release][release-img]][release] [![Build status][ci-img]][ci]
[![Coverage Status][coveralls-img]][coveralls]
[![License: Apache 2.0][license-img]][license]
[![Star on GitHub][stars-img]][stars] [![Discord][discord-img]][discord]
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:
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
Quick links
- 📥 Downloads
- 📚 Documentation
- 🚀 Quickstart guides:
- Desktop app
- CLI
- Kubernetes Operator
- 💬 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