Potencialize seu agente
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirOverview
ToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers. <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/images/toolhive-byline-white.svg"> <img src="docs/images/toolhive-byline-black.svg" alt="ToolHive logo" width="500"/> </picture> <br> # The open source MCP platform trusted by developers and enterprises [![Release][relea
Tools
No tool list yet. Remote servers get one after the first health check.
ToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Toolhive runs locally over stdio.
Last checked 2026-11-09. ToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers. <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/images/toolhive-byline-white.svg"> <img src="docs/images/toolhive-byline-black.svg" alt="ToolHive logo" width="500"/> </picture> <br> # The open source MCP platform trusted by developers and enterprises [![Release][relea
From the publisher
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:
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.
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.
Choose the interface that best fits your workflow.
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 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.
