Skip to main content

UI polish, auth server improvements, and configurable proxy timeouts

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.

Embedded auth server: Transparent token refresh and Redis TLS​

The embedded authorization server received two production-readiness improvements, both contributed by Aron at Muon Space:

  • Transparent upstream token refresh handles token expiration automatically in the background without interrupting active MCP sessions or requiring users to re-authenticate, so long-running workflows don't break when identity provider tokens expire.
  • TLS support for Redis token storage enables encrypted connections between the auth server and Redis, meeting compliance requirements for organizations operating in multi-tenant or zero-trust environments where network-level encryption is mandated by policy.

Cloud UI now supports display_name for MCP servers, so administrators can assign human-readable titles that appear throughout the interface instead of raw server identifiers. This release also fixes Claude Code deep link generation, which was previously producing incorrect URLs.

Desktop UI: Refreshed navigation​

Desktop UI navbar has been refactored to align with the updated Stacklok brand style, providing a cleaner and more consistent navigation experience across the app.

ToolHive Runtime: Configurable proxy timeout​

The streamable HTTP proxy previously used a hardcoded 30-second response timeout, which caused 504 Gateway Timeout errors for MCP tools that need more time to complete, such as tools querying large datasets or interacting with slow external APIs. The timeout is now configurable via the TOOLHIVE_PROXY_RESPONSE_TIMEOUT environment variable, with a more generous default.

Getting started​

For detailed release notes, check the project repositories:

You can find all ToolHive documentation on the Stacklok documentation site.