The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Agenthub Monitor listing page.
An MCP App server: it renders an interactive pipeline dashboard inside the host window (Claude Desktop, Claude Code, and other MCP App–capable clients) instead of returning a wall of text.
The dashboard shows two things side by side:
Point it at your own pipeline's JSON export and it becomes a live view of your runs. With no configuration it serves a built-in sample, so the UI is useful the moment you install it.
| Tool | What it does | Read-only |
|---|---|---|
show_agenthub_monitor | Renders the dashboard inline in the host | yes |
get_status | Returns the current pipeline state as structured JSON | yes |
trigger_action | Records an action request in the server's own state | no |
trigger_action does not execute anything. It annotates the server's in-memory state so the
dashboard can show that an action was requested. This server runs no commands, spawns no
processes, and makes no network calls.
Requires Python 3.10+. No third-party dependencies.
Add to your MCP client configuration:
AGENTHUB_STATE_FILE is optional. Without it the server returns sample data, flagged with
is_sample_data: true so it is never mistaken for a real run.
Write this JSON from your own CI, orchestrator, or test harness:
The file is re-read on every tool call, so the dashboard reflects whatever your pipeline last wrote.
Node status strings are passed through to the UI as-is; COMPLETED, RUNNING, PENDING and
FAILED get distinct colours.
The UI is exposed as an MCP resource at ui://agenthub/mcp-app.html with MIME type
text/html;profile=mcp-app. Hosts that support MCP Apps render it inline; hosts that do not can
still read it as an HTML document.
The server reads one local file (the one you name in AGENTHUB_STATE_FILE) and sends nothing
anywhere. See PRIVACY.md.
MIT — see LICENSE.