toolhive
ToolHive is a platform for running MCP servers in production. It has four parts. The Runtime deploys servers in containers via Docker or Podman locally, or on Kubernetes with an Operator, and can proxy remote MCP servers, with OpenTelemetry and Prometheus for monitoring and audit logging. The Registry Server holds a curated catalog of trusted servers, integrates with the official MCP registry and can verify provenance and signatures. The Gateway defines endpoints and access policies, supports SSO through OIDC/OAuth, can combine tools into a virtual MCP with a deterministic workflow engine and can filter tool descriptions to save tokens. The Portal is a cross-platform desktop app and browser UI for one-click installs.
The README stresses that each server runs in an isolated container with only the permissions it needs and that secrets are managed rather than stored in plaintext. Individual developers can start with the desktop UI or CLI, which can run any MCP server from a container image or build one from common package managers, manage encrypted secrets, control network isolation and test with the official MCP Inspector, then use the same ideas in the Kubernetes Operator. It auto-configures clients such as GitHub Copilot and Cursor. Quickstarts for the desktop app, CLI and Operator are at docs.stacklok.com, and the project is Apache licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-27
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 25
- Latest release
- v0.58.0 (2026-10-27)
- Open issues
- 398
- Recent issues with at least one comment
- 4/17
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #5860 vmcp: all VirtualMCPServer instances grow 2-3x in memory over ~24h regardless of client activity14 comments · 2026-07-17
- #4048 Distinguish tool discovery from tool invocation in authorization and audit12 comments · 2026-03-09
- #5321 Embedded auth server rejects DCR from confidential MCP clients (`token_endpoint_auth_method` hardcoded to `none`)9 comments · 2026-05-19
- #6831 Re-authorization walks the full upstream chain instead of evaluating existing credentials8 comments · 2026-10-15
- #6675 Add a group-aware UpstreamFilter implementation for the embedded auth server8 comments · 2026-09-17
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want MCP servers to run in isolated containers with scoped permissions and managed secrets, on Docker, Podman or Kubernetes.
- You want the same tooling from a laptop (desktop app or CLI) to a Kubernetes Operator.
- Your team needs a registry with provenance verification, an SSO-capable gateway and audit logging.
- You just want to run one MCP server: it needs Docker, Podman or Kubernetes and is heavier than starting the server directly.
- You want a single component: the Runtime, Registry, Gateway and Portal take time to understand, and parts live in separate repositories.
- You expect container isolation to replace reviewing what each server can reach.
How it differs
vs archestra★ 4.4kToolHive is a runtime and registry for MCP servers, under an Apache licence. Archestra is a broader enterprise platform with chat, LLM and MCP gateways, and dual AGPL and commercial licensing.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!