delivery-surface-backlog
v1.9.0A run surface that is an application: the Backlog desktop app. A stdio MCP server that forwards the lifecycle operations of the surface capability (open_dashboard, start_run, record_prompt, set_run_context, update_stage, finish_run, list_runs, get_run) to the MCP endpoint inside the running app, with the bearer token from the app's own settings, and passes Backlog's answers and refusals through unchanged; export_report only while Backlog lists it, render never. With Backlog closed or its MCP server off, open_dashboard answers unavailable so a caller moves on to the next surface. Registering Backlog's own backlog server, the tracker, never makes it a surface; installing this plugin does. Declares no dependency and names no engine.
By Job SchepersLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 26, 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-backlog for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install delivery-surface-backlog@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/devbookClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/delivery-surface-backlog/.
Plugin files
├── .claude-plugin/plugin.json└── .mcp.json
MCP servers1
- command
- node
- args
- ${CLAUDE_PLUGIN_ROOT}/mcp/delivery-surface-backlog/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-backlog",
"version": "1.9.0",
"description": "A run surface that is an application: the Backlog desktop app. A stdio MCP server that forwards the lifecycle operations of the surface capability (open_dashboard, start_run, record_prompt, set_run_context, update_stage, finish_run, list_runs, get_run) to the MCP endpoint inside the running app, with the bearer token from the app's own settings, and passes Backlog's answers and refusals through unchanged; export_report only while Backlog lists it, render never. With Backlog closed or its MCP server off, open_dashboard answers unavailable so a caller moves on to the next surface. Registering Backlog's own backlog server, the tracker, never makes it a surface; installing this plugin does. Declares no dependency and names no engine.",
"author": {
"name": "Job Schepers"
},
"license": "MIT",
"keywords": [
"surface",
"backlog",
"runs",
"mcp",
"proxy"
],
"mcpServers": {
"delivery-surface-backlog": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/mcp/delivery-surface-backlog/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-backlog on Agent Plugins Marketplace](https://pluginsmp.com/plugins/delivery-surface-backlog)