toolhive

Why we included this project

Once an organization adopts the Model Context Protocol, sprawl follows fast: developers stand up MCP servers ad hoc, nobody can see what's actually running, and credentials end up scattered. ToolHive addresses that by running every MCP server in an isolated container with a minimal permission file, so a model can call tools without ever touching local secrets. Connect an authentication source and you get per-request identity enforcement, audit logs, OTel traces, and a Kubernetes operator that fits existing infrastructure rather than demanding a new setup. For teams whose compliance rules forbid sensitive data going to SaaS MCP providers, the self-hostable registry and gateway keep data in-house while still providing the observability and policy controls you'd want in production. If you're a platform or security engineer deciding how to govern MCP usage, this is the infrastructure layer to pilot before you let agents run loose.