loading…
Search for a command to run...
loading…
A lightweight utility designed to simplify the deployment and management of MCP servers, ensuring ease of use, consistency, and security through containerizatio
A lightweight utility designed to simplify the deployment and management of MCP servers, ensuring ease of use, consistency, and security through containerization by [StacklokLabs](https://github.com/StacklokLabs)
Release Build status Coverage Status License: Apache 2.0 Star on GitHub Discord
ToolHive runs every MCP server in an isolated container, enforces identity and access policy per request, 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 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 |
ToolHive architecture: Gateway, Registry Server, Runtime, and Portal
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.
Curate a catalog of trusted servers your teams can quickly discover and deploy.
Deploy, run, and manage MCP servers locally or in a Kubernetes cluster with security guardrails.
Simplify MCP adoption for developers and knowledge workers across your enterprise
Individual developers can get started in minutes with the desktop UI or CLI, then apply the same concepts in enterprise environments.
Key features:
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:
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 access approved MCP servers through a secure, browser-based cloud UI. Developers can also connect using the ToolHive CLI or desktop UI for advanced integration and testing workflows.
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.
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"toolhive": {
"command": "npx",
"args": []
}
}
}