Agenthub Monitor

io.github.NEVELSK65Published by GitHub account NEVELSK65v1.0.0Updated Oct 24, 2026

Renders a pipeline DAG and test-harness dashboard inline as an MCP App

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

An MCP App server that renders an interactive pipeline DAG and test-harness dashboard inline in the host, reading state from a local JSON file.

What you can do
Render the pipeline dashboard inline in an MCP App-capable host, showing DAG nodes grouped into waves with per-node status and harness metrics such as pass rate, critical failures, cost and latency. Return the current pipeline state as structured JSON. Record an action request in the server's own in-memory state so the dashboard can show it was requested. Serve a built-in sample flagged as sample data when no state file is configured.
When to use it
Useful when you want a live visual view of a CI, orchestrator or test-harness pipeline run inside Claude Desktop or another MCP App-capable client, rather than reading raw status output. Also handy for previewing the dashboard with built-in sample data before wiring up your own state file.
Requirements
Runs locally as a Python process (Python 3.10+, no third-party dependencies) over stdio. Optionally set AGENTHUB_STATE_FILE to the absolute path of a JSON file in the documented format; without it the server serves sample data. No authentication or network access needed.
Before you install
The state file is re-read on every tool call, so anything written there is shown in the dashboard. trigger_action only annotates in-memory state and executes nothing, so it is not a way to actually run pipeline actions. Node status strings are passed through to the UI as-is.

Installation

In SourceWeft

  1. Open Agenthub Monitor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

AgentHub Monitor

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:

  • DAG state — nodes of a pipeline run, grouped into waves, each with its own status.
  • Harness metrics — scenario pass rate, critical failures, accumulated cost and latency.

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.

Tools

ToolWhat it doesRead-only
show_agenthub_monitorRenders the dashboard inline in the hostyes
get_statusReturns the current pipeline state as structured JSONyes
trigger_actionRecords an action request in the server's own stateno

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.

Install

Requires Python 3.10+. No third-party dependencies.

bash
git clone https://github.com/NEVELSK65/mcp-agenthub-monitor.gitcd mcp-agenthub-monitorpython3 -m unittest discover -s tests    # optional: verify

Configure

Add to your MCP client configuration:

json
{  "mcpServers": {    "agenthub-monitor": {      "command": "python3",      "args": ["/absolute/path/to/mcp-agenthub-monitor/server.py"],      "env": {        "AGENTHUB_STATE_FILE": "/absolute/path/to/your/pipeline-state.json"      }    }  }}

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.

State file format

Write this JSON from your own CI, orchestrator, or test harness:

json
{  "dag": {    "title": "Nightly build",    "total_nodes": 6,    "completed_nodes": 4,    "waves": 3,    "node_states": {      "node_01_checkout": "COMPLETED",      "node_02_unit_tests": "COMPLETED",      "node_03_integration": "RUNNING",      "node_04_security_scan": "PENDING"    }  },  "harness": {    "pass_rate_pct": 93.75,    "total_scenarios": 16,    "passed_scenarios": 15,    "critical_failures": 0,    "total_cost_usd": 0.112,    "total_latency_ms": 41700  },  "log": "Integration stage in progress."}

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.

Resource

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.

Privacy

The server reads one local file (the one you name in AGENTHUB_STATE_FILE) and sends nothing anywhere. See PRIVACY.md.

License

MIT — see LICENSE.

Source: README.md at commit 0501d15

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts