ToolHive v0.20.0 introduces stateless remote server support for POST-only MCP endpoints, shared telemetry configuration for vMCP, non-standard OAuth scope parameter handling, and expands skills support to over a dozen AI coding agents. This release also includes a breaking change to the groupRef field format across all CRD types.

This week brings a major Playground upgrade in the ToolHive Desktop UI with threaded chat and MCP Apps, claim-based authorization across the Registry Server for fine-grained access control, and per-user, per-tool call rate limiting for MCPServers in Kubernetes.

ToolHive now supports agent skills - reusable bundles of instructions and configuration that teach AI agents how to perform specific tasks. MCP servers give agents the raw tools they can call; skills give them the knowledge of when, why, and how to use those tools effectively. With ToolHive, teams can create skills, publish them to a registry, and install them across supported AI clients from a single CLI.

This week's updates improve how MCP servers surface in the Cloud UI, harden the embedded authorization server for production deployments, refresh the Desktop UI with updated branding, and add configurable proxy timeouts for long-running MCP tools.

MCP Optimizer capabilities are now embedded directly in vMCP, bringing the same token reduction and improved tool selection per request from desktop to Kubernetes-native deployments. Instead of every developer configuring a local optimizer instance, platform teams deploy it once and every connected client benefits automatically.

This week brings enterprise readiness and resilience improvements across ToolHive. The new embedded authorization server lets users authenticate to MCP servers through their company identity provider, no locally stored credentials required. vMCP adds circuit breakers that prevent cascading failures when backends degrade, and the Registry Server gains cluster-wide namespace scanning for multi-tenant Kubernetes deployments.

This week delivers capabilities that production teams need: vMCP now auto-discovers backend servers without restarts and reports operational health in CRD status fields, the Registry gains OpenTelemetry support and tool definition APIs, and both the CLI and Desktop UI add custom header configuration for remote MCP connections. We've also added custom CA support for organizations running private identity providers.

Welcome to 2026! The ToolHive team is back into the swing of things after the holiday break, focusing on improved operational resilience and streamlined developer workflows: vMCP gained backend health monitoring for production environments, the CLI and desktop UI added bearer token authorization for remote servers, the desktop UI added flexible proxy configuration, and Cloud UI now displays MCP configurations for your IDE clients, with one-click setup for Cursor.

This week ToolHive added production-ready features that teams need for enterprise deployment: audit logging and health monitoring for vMCP, API-driven registry management, and direct registry connections in the UI.

This week, we focused on operational readiness and flexibility: the Registry Server now auto-discovers server types and scales sync across multiple registry instances, Virtual MCP Server (vMCP) gained OpenTelemetry observability and smarter composite tools, and both the CLI and UI now fully support the ToolHive Registry Server.