MCP server ToolHive

The 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:
  • 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
• 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

1. Admins curate and organize MCP servers in the Registry, configuring access and policies.
2. Users discover, configure, and run MCP servers through ToolHive UI or the CLI, and ToolHive orchestrates deployment and access.
3. 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.
4. 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!

• 🐛 Report issues
• 💬 Join our Discord

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):

• 🤝 Contributing guide
• 📖 Developer guides
• 📐 Architecture documentation

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.