delivery-surface-dashboard
v1.0.0A run surface: the live dashboard a run is watched in. An MCP server implementing all three surface capability groups — lifecycle (open_dashboard, start_run, record_prompt, set_run_context, update_stage, finish_run, list_runs, get_run), render (render_diagram, render_markdown), and export (export_report) — with a run timeline carrying stage output, QA scenarios and their evidence, a Mermaid diagram viewer and a Markdown document viewer, and hook-captured tool and token telemetry. Rendered inline as an MCP App where the host supports it, served on 127.0.0.1 where it does not. Declares no dependency and names no engine.
By Job SchepersLicense: MIT0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 14, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install delivery-surface-dashboard for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install delivery-surface-dashboard@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/JSdotNet/ai-agent-stackClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/delivery-surface-dashboard/.
Plugin files
├── .claude-plugin/plugin.json└── .mcp.json
MCP servers1
- command
- node
- args
- ${CLAUDE_PLUGIN_ROOT}/mcp/delivery-surface-dashboard/mcp-server.mjs
MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.
Plugin manifests1
{
"name": "delivery-surface-dashboard",
"version": "1.0.0",
"description": "A run surface: the live dashboard a run is watched in. An MCP server implementing all three surface capability groups — lifecycle (open_dashboard, start_run, record_prompt, set_run_context, update_stage, finish_run, list_runs, get_run), render (render_diagram, render_markdown), and export (export_report) — with a run timeline carrying stage output, QA scenarios and their evidence, a Mermaid diagram viewer and a Markdown document viewer, and hook-captured tool and token telemetry. Rendered inline as an MCP App where the host supports it, served on 127.0.0.1 where it does not. Declares no dependency and names no engine.",
"author": {
"name": "Job Schepers"
},
"license": "MIT",
"keywords": [
"surface",
"dashboard",
"runs",
"mcp",
"mermaid",
"markdown"
],
"mcpServers": {
"delivery-surface-dashboard": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/mcp/delivery-surface-dashboard/mcp-server.mjs"
]
}
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[delivery-surface-dashboard on Agent Plugins Marketplace](https://pluginsmp.com/plugins/delivery-surface-dashboard)