Introduction
The ToolHive Cloud UI is a web application that gives your team a shared catalog of MCP servers. It connects to a Registry Server and displays every registered server in a browsable interface, so team members can discover available servers and copy connection URLs into their AI agents or clients.
Use the Cloud UI when you want to:
- Give your team a single place to discover MCP servers without using the CLI or desktop app.
- Provide a self-service catalog where users copy server URLs directly into their AI workflows.
- Layer authentication on top of the catalog with your existing identity provider (IdP).
The Cloud UI is a read-oriented catalog that works alongside the Registry Server. It does not start or stop MCP servers. To manage server lifecycles, use the ToolHive CLI, ToolHive UI, or Kubernetes Operator.
Stacklok Enterprise includes an enhanced Cloud UI that builds on the open source catalog with full management capabilities. Browse and install skills, and manage registry sources and entries directly from the web interface.
Architecture overview
The Cloud UI is a Next.js application with two main dependencies:
- Registry Server - provides the MCP server catalog through the MCP Registry API. The Cloud UI reads server entries from this API.
- OIDC provider - handles user authentication. The Cloud UI uses Better Auth with any standards-compliant OIDC provider (Okta, Microsoft Entra ID, Auth0, and others).
Next steps
- Deploy the Cloud UI on Kubernetes with the Helm chart, a Registry Server, and your OIDC provider.
- Configure the Cloud UI with environment variables and OIDC settings.