feat(cli): add thv tui command for an interactive terminal UI experience

[peppescg]

Summary

Add a thv tui command that launches an interactive terminal user interface (TUI) for ToolHive, improving the overall user experience for users who prefer to manage their MCP servers directly from the terminal without relying on a separate web UI.

Background

ToolHive already provides a solid CLI experience, but some workflows — such as inspecting running servers, browsing logs, or exploring the registry — benefit from a richer, interactive interface. A TUI improves the current user experience and integrates UI-style functionality directly in the terminal, without requiring users to switch to a browser or remember individual subcommands.

Proposed Solution

Introduce a thv tui subcommand that opens an interactive terminal UI (e.g. built with Bubble Tea / Lip Gloss). The TUI should include the following views:

• Running MCP list — overview of all currently running MCP servers
• MCP detail — info panel for a selected running MCP (metadata, status, configuration)
• Logs viewer — MCP server logs and proxy logs, with in-view search/filtering
• Tools list — list of tools exposed by a running MCP, each with its description
• Registry list — browse servers available in the configured registry, with descriptions
• MCP Inspector — interactive panel to craft MCP request payloads, send them to a running MCP, read the JSON response, and copy it to the clipboard

Acceptance Criteria

• `thv tui` launches without errors and renders a functional TUI
• All views listed above are implemented and navigable from within the TUI
• Logs viewer supports search/filtering within the log output
• MCP Inspector allows configuring the request payload, displays the JSON response, and supports copying to clipboard
• The command is documented in `--help` output and in the project docs
• Unit/integration tests cover the core TUI logic

[eleftherias]

Note about listing tools, we can't list them for STDIO servers because that calls the initialize request, which means when the real client tries to call initialize it can get unexpected behaviour.
This is a problem even if the STDIO server is proxied by streamable HTTP because ToolHive still forwards the initialize request.

[peppescg]

Note about listing tools, we can't list them for STDIO servers because that calls the initialize request, which means when the real client tries to call initialize it can get unexpected behaviour. This is a problem even if the STDIO server is proxied by streamable HTTP because ToolHive still forwards the initialize request.

Thanks, I will take a look specifically with a stdio mcp, and possibly remove those features that cannot work