[opensourcedex]

toolhive is a free, open source ai security & privacy project written in Go and released under Apache-2.0. It has 2,187 GitHub stars, 297 forks and 369 open issues, and was last pushed 5 hours ago. On this registry it ranks #14 of 34 tracked projects in AI Security & Privacy, with 5 head-to-head comparisons available. It gained 12 stars over the last 3 tracked days.

What is toolhive?

What it is

ToolHive is an open-source, Apache-2.0 licensed platform written in Go for running and managing Model Context Protocol (MCP) servers. It lives in the AI and machine learning ecosystem, specifically MCP tooling and AI security and privacy. The project addresses the problem of exposing MCP servers to AI coding assistants and enterprise clients without broad local access or unmanaged behavior.

The concrete problem is that developers can run MCP servers informally, creating shadow use, weak access control, and limited visibility for platform teams. ToolHive places each MCP server in an isolated container, applies identity and access policy per request when an authentication source is configured, and gives teams observability for production use. It supports self-hosted deployment for organizations whose compliance requirements prevent sensitive information from being processed by hosted SaaS MCP solutions.

Key capabilities

  • Gateway defines dedicated endpoints for tool access and can orchestrate multiple tools into a virtual MCP server through a deterministic workflow engine.
  • Gateway centralizes security policy, authentication, authorization, and auditing, and it integrates with an identity provider for OIDC/OAuth compatible single sign-on.
  • Gateway can filter tools and descriptions to improve performance and reduce token usage, with the README stating that semantic tool search can reduce token usage by up to 85 percent.
  • Registry Server curates trusted MCP servers, integrates with the official MCP registry, allows custom servers, and supports grouping servers by role or use case.
  • Registry Server supports API-driven management, provenance verification, server signing, and preset configurations and permissions for deployment.
  • Runtime deploys and manages MCP servers locally or in a Kubernetes cluster with security guardrails, and the project includes a Kubernetes operator for policies and observability.
  • ToolHive connects clients such as Claude Desktop, Cursor, VS Code, Claude Code, GitHub Copilot, or other preferred clients to MCP servers through a single click or command.

Who uses it and how

  • Developers use ToolHive to run MCP servers with container isolation and reduced token consumption while connecting them to coding assistants such as Claude Code, Cursor, or GitHub Copilot.
  • Platform engineers use ToolHive to run MCP servers on existing Kubernetes infrastructure, where they can declare policies, integrate with an identity provider, and emit OTel traces.
  • Enterprises use ToolHive to self-host an MCP registry and gateway so that sensitive information does not need to pass through a hosted SaaS provider.
  • Security teams use ToolHive to reduce shadow MCP use by enforcing configurable identity controls and obtaining audit logs for MCP server access.

Getting started

Users can download ToolHive from the Stacklok download page and follow quickstart guides for the desktop app, CLI, or Kubernetes operator. The README also points to Kubernetes operator documentation and Stacklok Enterprise comparison materials.

When to use it — and when not to

ToolHive is suitable when an organization needs a self-hosted MCP platform with container isolation, policy enforcement, registry governance, and Kubernetes-based operations, especially when SaaS MCP services conflict with compliance requirements. It is less suitable when a team wants a fully managed hosted service with no infrastructure to operate, because the open-source project requires running a gateway, registry, runtime, and related integrations such as an authentication source and observability stack. The project has 369 open issues, and the README notes that Stacklok offers added capabilities and expert support when scaling beyond the open-source pilot.

project readme (upstream, from github) — read inline

The open source MCP platform trusted by developers and enterprises

[![Release][release-img]][release] [![Build status][ci-img]][ci] [![Coverage Status][coveralls-img]][coveralls] [![License: Apache 2.0][license-img]][license] [![Star on GitHub][stars-img]][stars] [![Discord][discord-img]][discord]

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:

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 configurable 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

Quick links

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 team

readme truncated — read the full docs on github

Frequently asked questions

Is toolhive free to use?

toolhive is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does toolhive do?

ToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers.

What is toolhive written in?

toolhive is primarily written in Go. Its source is publicly available at https://github.com/stacklok/toolhive, and it has 2,187 GitHub stars.