toolhive-studio

ToolHive Studio is an experimental desktop UI that lets you discover, deploy, and manage MCP servers in secure, isolated containers. It acts as a front-end orchestration layer: you can browse available MCP server images, spin up instances in locked-down containers, and expose them through a built-in proxy so MCP clients can reach them safely. Within ToolHive Studio you’ll find a graphical workflow to configure a server, choose the runtime container, manage access permissions, and monitor usage and telemetry (telemetry can be opted out). The platform is designed to work with a wide range of MCP servers—simply select a server image, configure environment variables, and launch. Tools are provided to update containers, scale resources, and connect clients through the proxy without exposing sensitive data. If you need CLI or Kubernetes integration, ToolHive also offers commands and operator support to run MCP servers in alternative environments, but the Studio focuses on quick, secure deployments via the UI.

Prerequisites:

• A supported host with Node.js and npm/npx or an environment where you can run containers if you prefer the container path.
• Internet access to fetch MCP server images via npx or other package managers.

Install and run ToolHive Studio:

1. Ensure Node.js and npm are installed

   • On macOS/Linux: install via your package manager or from nodejs.org
   • On Windows: install via the Node.js installer from nodejs.org

2. Run ToolHive Studio using npx (recommended for quick start)

   • This will fetch the ToolHive Studio package and start the UI with a secure runtime for MCP servers

   Command:

   • npx -y toolhive-studio

3. Alternative (if you have a packaged installer or want to run locally):

   • Follow the repository’s published installation guide for your platform, which may include a downloadable installer or Docker-based setup.

4. First run guidance

   • Launch the Studio and log in if required
   • Use the Quickstart workflow to browse MCP server images, configure environment variables, and start a server in a protected container

Notes:

• Ensure outbound network access for pulling images and updates.
• If you encounter network or permission issues, check container runtime permissions and firewall rules.
• Telemetry can be disabled in Settings if desired.

Tips and commonly used options:

• Environment variables: You may configure per-server environment variables to customize behavior. The Studio typically exposes a UI to set these; in CLI or automated usage, you can pass them via the MCP runtime configuration.
• Telemetry: ToolHive collects error reports and performance metrics by default. You can opt out in Settings.
• Security: Each MCP server runs in an isolated container with minimum required permissions. Do not expose privileged ports or secrets in plain text; use the Studio’s secret management features where available.
• Networking: The built-in HTTP/SSE proxy bridges MCP clients to servers. Ensure the proxy port is accessible to clients and that container networks are correctly configured.
• Upgrades: When updating MCP server images, use the Studio’s upgrade workflow to avoid breaking client connections.
• Troubleshooting: If a server fails to start, check container logs via the Studio’s monitoring panel and verify environment variable configurations. Review any recent changes to the MCP image or runtime permissions.