Skip to main content

Using the ToolHive Kubernetes Operator

Introduction​

The ToolHive Kubernetes Operator brings MCP servers into a shared, governable Kubernetes environment. It solves the gap between trying MCP locally and running it for teams, with standard deployment workflows, centralized policy control, and platform-managed connectivity.

Within the ToolHive platform, the operator is the foundation for multi-user and production-style deployments. It runs MCP workloads in the cluster and unlocks capabilities like Virtual MCP Server (vMCP) and Registry Server integrations.

You define MCP servers as Kubernetes custom resources and the operator automates their deployment, proxying, and lifecycle management. The operator supports several primary resource types:

  • MCPServer: run a containerized MCP server inside your cluster
  • MCPRemoteProxy: proxy an MCP server hosted outside your cluster
  • MCPServerEntry: register a remote MCP server as a catalog entry for vMCP discovery
  • VirtualMCPServer: aggregate and optimize multiple servers behind a single endpoint

This is the best starting point when you need ToolHive in a shared, multi-user, or production-style Kubernetes environment.

Where to start​

Contents​