Studio (TUI)

Studio is mcphub's interactive terminal UI — the same mcphub.yaml and intelligence store the CLI uses, browsable and toggleable without hand-editing YAML or an agent's config file. It's built on charm.land/bubbletea/v2 and charm.land/lipgloss/v2, with charmbracelet/harmonica driving spring-animated stat bars on the Stats tab.

mcphub studio    # alias: tui

It runs in the alternate screen, so it takes over the terminal and restores it cleanly on exit.

Layout

A header line shows the server/enabled/expose/agent counts, then three tabs:

• Servers — every server in mcphub.yaml, each showing an on/off mark, a pin marker (📌) for pinned servers, its name, kind (stdio or remote), and description. The cursor (▶) marks the current row.
• Agents — each harness mcphub syncs into, with its type, mode, how many servers mcphub currently manages there, and its config path. Agents with per-agent routing show their servers/tools scope on a second line. Agents that have a config file on disk but aren't declared in mcphub.yaml show up as available — add them to agents: (or run mcphub init --from-agents) to start syncing them.
• Stats — the same local intelligence mcphub stats reports: total calls, estimated tokens, and errors, followed by harmonica spring-animated per-server call bars that ease toward their target length whenever you switch onto the tab.

Keys

Key	Action
↑ / k, ↓ / j	move the cursor
space / enter	toggle the selected server on/off (Servers tab)
p	pin/unpin the selected server (Servers tab)
s	open the sync panel — preview a dry run, then a to apply
a / enter	apply the previewed sync (inside the sync panel)
esc / q	close the sync panel without applying
x	flip exposure between all and lazy
tab / → / l, shift+tab / ← / h	next / previous tab
1 / 2 / 3	jump to Servers / Agents / Stats
r	reload mcphub.yaml and the stats from disk
q / ctrl+c	quit

Toggling persists immediately

Press space on a server and Studio writes the change to mcphub.yaml right away — the same effect as mcphub enable / mcphub disable. The status line confirms it and reminds you that toggling only changes the config:

• vecgrep enabled — press s to sync agents

Toggling does not touch your agents. As with the CLI, you push the result to your harnesses with s in Studio, or mcphub sync from the shell, once you're happy with the set.

Preview then apply: s → a

Press s from any tab to open the sync panel: a dry-run preview of the exact changes mcphub would make to every agent, computed with the same reconcile engine mcphub sync uses. Nothing is written yet. Press a (or enter) to apply it — this is the equivalent of running mcphub sync --write from the shell, backup and all — or esc to back out. The panel always covers every enabled agent; to sync just one, use mcphub sync <agent> --write from the shell instead.

Preview costs nothing

Opening the sync panel never mutates anything — it's the same dry-run guarantee as the CLI. You can open it just to see current drift, then back out without applying.

Flipping exposure: x

x toggles the top-level expose field in mcphub.yaml between all (every downstream tool mounted as server__tool) and lazy (only the seven gateway meta-tools advertised, with the rest discovered on demand). See Exposure: all vs. lazy for what each mode costs and buys you. As with a pin change, an exposure flip takes effect the next time mcphub mcp serve starts — restart your agents to pick it up.

Reloading

Press r to re-read mcphub.yaml and refresh the stats. Handy if you edited the config in another pane, or an agent has made calls through the gateway since you opened Studio and you want to see the updated numbers.

Studio vs. the CLI

Studio and the CLI operate on the exact same files — nothing you do in one is invisible to the other. Reach for whichever fits the moment:

• Studio for interactive sessions: skimming what's enabled across a dozen servers, toggling a handful on or off while eyeballing the effect, checking which agents have drifted, or watching which servers are actually earning calls before you decide what to disable.
• The CLI for anything scripted, repeatable, or automated: CI, a one-off mcphub enable codemap && mcphub sync --write, --json/--markdown output for tooling or notes, or driving mcphub from another agent.

Everything maps directly:

Studio	CLI equivalent
space on a server	mcphub enable / mcphub disable
p on a server	mcphub pin / mcphub unpin
x	editing expose: in mcphub.yaml
s → a	mcphub sync → mcphub sync --write
Stats tab	mcphub stats
Agents tab	mcphub agents / mcphub status

Next

• Sync to your agents — what the sync panel's preview and apply actually do, per harness.
• Intelligence — what the Stats tab is showing you.
• Concepts — gateway vs. direct, exposure, and pins.