Build
Connect & operate
Design & teams
Start hereScope a build in one callBring a spec, a wireframe, or a paragraph. You leave with an architecture, a timeline, and a number.Book a scoping call
AI software
LLM & data systems
Vibe coding
Ready to ship?Put AI where the work isAgents, RAG, and private LLMs wired into the systems your team already uses — not a chatbot bolted to a homepage.Discuss an AI project
Domain firstWe learn your workflow before we model itRegulated, operational, or high-volume — the constraints belong in the schema, not in a training doc.Talk about your domain
Plan smarterEstimate before you commitCost ranges, scope templates, and the questions we ask in discovery — free, no form.Open the cost calculator
Real conversationsTalk with a technical leadNo SDR, no discovery gauntlet. The person on the call is the one who scopes the build.Book a call
MCP Servers · stacklok

toolhive

ToolHive is an open-source platform for securely running and managing Model Context Protocol (MCP) servers across desktop, Kubernetes, and hybrid environments. It isolates MCP servers in containers, enforces identity and access policies, and provides observability for enterprise adoption of AI tools.

Source: GitHub — github.com/stacklok/toolhive
1.9k
GitHub stars
240
Forks
Go
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorystacklok/toolhive
Ownerstacklok
Primary languageGo
LicenseApache-2.0 — OSI-approved
Stars1.9k
Forks240
Open issues248
Latest releasev0.34.0 (2026-07-07)
Last updated2026-07-08
Sourcehttps://github.com/stacklok/toolhive

What toolhive is

Built in Go, ToolHive comprises a modular architecture (Gateway, Registry Server, Runtime, Portal) that orchestrates MCP server lifecycle, enforces fine-grained access control via OIDC/OAuth integration, runs servers in isolated containers, and exports OpenTelemetry traces and Prometheus metrics for observability.

Quickstart

Get the toolhive source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/stacklok/toolhive.gitcd toolhive# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Enterprise self-hosting of MCP servers

Organizations with data residency or compliance requirements can self-host the entire ToolHive platform (registry, gateway, runtime) on-premises or private cloud, maintaining full control over sensitive information and audit trails.

Kubernetes-native MCP fleet management

Platform engineers can declaratively manage MCP server deployments, access policies, and IdP integration using Kubernetes Custom Resource Definitions and familiar YAML workflows, with built-in multi-namespace isolation and ingress support.

Developer productivity with token-optimized MCP access

Individual developers and small teams can run local MCP servers via Docker/Podman with semantic tool search and token optimization (claimed up to 85% savings), encryption, and network isolation without managing credentials locally.

Implementation considerations

  • Requires Docker/Podman for local deployments or a functional Kubernetes cluster (with operator support) for enterprise use; evaluate existing infrastructure compatibility.
  • Identity integration via OIDC/OAuth is available but requires configuration; audit requirements and SSO architecture mapping before deployment.
  • Container image supply and MCP server catalog curation (via Registry Server) requires planning; decide whether to use official MCP registry, build custom images, or proxy external servers.
  • OpenTelemetry and Prometheus integration for observability is included; ensure monitoring stack compatibility and alert configuration before production.
  • Isolated container execution per request may increase latency and resource consumption; benchmark token savings claims and performance against your typical MCP server usage patterns.

When to avoid it — and what to weigh

  • You need a fully managed, zero-ops SaaS solution — ToolHive is open-source and requires self-hosting, operational maintenance, and infrastructure provisioning. If you want minimal operational overhead, consider managed alternatives.
  • Your environment does not support containerization — ToolHive's core design relies on Docker/Podman containers (desktop) or Kubernetes (enterprise). Organizations without container runtimes cannot easily adopt this platform.
  • You lack Kubernetes expertise for enterprise deployment — The Kubernetes operator requires Kubernetes cluster management knowledge. Enterprises without K8s operations teams may face significant learning curve and ongoing maintenance burden.
  • You need proven, stable production track record — ToolHive was created 2025-03-12 and is at v0.34.0 (released 2026-07-07). The project is active but relatively young; long-term production stability and maintenance guarantees are Unknown.

License & commercial use

ToolHive is released under Apache License 2.0 (Apache-2.0), a permissive OSI-approved open-source license. It permits commercial use, modification, and distribution, provided license and copyright notices are retained and liability disclaimers are honored.

Apache-2.0 is a permissive open-source license that allows commercial use without requiring proprietary source code disclosure. However, verify whether Stacklok's commercial terms, support obligations, or dual-licensing arrangements impose additional restrictions; the README references 'Stacklok Enterprise' as a commercial variant, suggesting potential commercial licensing considerations. Consult legal counsel if your use case involves proprietary modifications or commercial redistribution.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityHigh
DEV.co fitGood
Assessment confidenceHigh
Security considerations

ToolHive implements per-server container isolation, identity-based access policies (OIDC/OAuth), audit logging, and OpenTelemetry tracing. Container isolation reduces blast radius of compromised MCP servers. However, ensure: (1) container runtime security hardening (Pod Security Standards, network policies); (2) secret management strategy (encrypted local storage, Kubernetes Secrets integration); (3) identity provider security posture; (4) audit log retention and access control. No formal security audit, penetration test results, or CVE history provided; conduct threat modeling aligned with your risk profile. Requires security review before production deployment.

Alternatives to consider

Anthropic Claude API (managed MCP)

Fully managed, zero-ops service if you accept SaaS deployment; no self-hosting or Kubernetes overhead, but less control over data residency and custom server integration.

LangChain / LlamaIndex framework-based MCP wrappers

Lightweight, framework-integrated MCP orchestration without standalone platform overhead; suitable for application-embedded use but lacks enterprise registry, policy enforcement, and observability.

Stacklok Enterprise (commercial variant)

Managed platform with added capabilities, expert support, and SaaS or on-premises options; eliminates self-hosting burden but requires commercial licensing and vendor lock-in.

Software development agency

Build on toolhive with DEV.co software developers

Download ToolHive, explore the Kubernetes operator, or review the enterprise variant. Start with the quickstart guide (desktop, CLI, or K8s) and join the Discord community for support.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

toolhive FAQ

Can I run ToolHive without Kubernetes?
Yes. Desktop users can run MCP servers locally using Docker/Podman via the CLI or UI. Kubernetes is only required for enterprise fleet management and centralized policy enforcement.
Does ToolHive support existing MCP servers from the official registry?
Yes. ToolHive includes a Registry Server that integrates with the official MCP registry and allows you to add custom servers, curate catalogs by role, and manage permissions.
What is the claimed token savings?
README states up to 85% token usage reduction via semantic tool search and filtering. This is a claim; independent benchmark results are not provided. Test with your typical MCP server usage before relying on this number.
Is Stacklok Enterprise required for production?
No. Open-source ToolHive can be deployed to production. Stacklok Enterprise is a commercial variant with added capabilities and expert support; it is optional.

Software development & web development with DEV.co

Pairing toolhive with the rest of your stack is where most mcp servers projects stall. DEV.co is a software development agency that does the integration work — plus AI development when models are in scope.

Ready to secure and scale MCP servers?

Download ToolHive, explore the Kubernetes operator, or review the enterprise variant. Start with the quickstart guide (desktop, CLI, or K8s) and join the Discord community for support.