This week, ToolHive Studio v0.35.0 takes Agents in the Playground out of feature-flag and ships them to everyone, with two built-in agents and the option to author your own. Studio also retires the localhost TCP port it used to talk to ToolHive in favor of a per-user socket, and the Playground picks up message editing, queueing, and per-message cost.

This week, the embedded auth server runs on the Redis topology your platform already uses (standalone, cluster, or Sentinel), and the ToolHive CLI authenticates MCP clients without dynamic client registration.

This week, the ToolHive Desktop UI installs skills directly into the AI clients you already use, and Virtual MCP Server (vMCP) is now supported locally. The Registry Server also surfaces version information in list views.

This week brings Registry Server v1.2.0 with stronger access control over published entries and a clean break from the legacy format. Virtual MCP Server (vMCP) and MCP servers gain horizontal scaling support with Redis-backed session routing to keep sessions consistent across replicas.

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.