oleks/pipetree
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Wrap pipetree as an MCP server (scan / filter / pipeline_health tools) #7

New Issue
Open
opened 2026-08-01 15:42:41 +03:00 by oleks · 0 comments
oleks commented 2026-08-01 15:42:41 +03:00
Owner
Copy Link
Copy Source

SPEC.md roadmap item 6 — the original motivating use case for this
project: let an agent audit CI architecture across the fleet directly.

Once #1 (filtering/rollups) and #4 (live health) stabilize the JSON shape,
expose it as MCP tools, e.g.:

  • scan — the current tree/JSON scan, parameterized like the CLI flags.
  • filter — the rollup/filter mode from #1.
  • pipeline_health — the live-status layer from #4.

Depends on #1 and #4 (JSON shape needs to be stable first, per SPEC.md).

Source: SPEC.md.

Acceptance criteria

  • MCP server exposes scan, filter, pipeline_health tools matching the CLI's equivalent flags/output
  • tool schemas documented (inputs, outputs) so an agent can discover them without reading the Go source
  • exercised end-to-end by an actual agent call, not just unit-tested
  • wired into the appropriate plugin/registry for this environment (matches how other MCP tools in this fleet are packaged)
SPEC.md roadmap item 6 — the original motivating use case for this project: let an agent audit CI architecture across the fleet directly. Once #1 (filtering/rollups) and #4 (live health) stabilize the JSON shape, expose it as MCP tools, e.g.: - `scan` — the current tree/JSON scan, parameterized like the CLI flags. - `filter` — the rollup/filter mode from #1. - `pipeline_health` — the live-status layer from #4. Depends on #1 and #4 (JSON shape needs to be stable first, per SPEC.md). Source: [SPEC.md](https://git.oleks.space/oleks/pipetree/src/branch/main/SPEC.md#roadmap). ## Acceptance criteria - [ ] MCP server exposes `scan`, `filter`, `pipeline_health` tools matching the CLI's equivalent flags/output - [ ] tool schemas documented (inputs, outputs) so an agent can discover them without reading the Go source - [ ] exercised end-to-end by an actual agent call, not just unit-tested - [ ] wired into the appropriate plugin/registry for this environment (matches how other MCP tools in this fleet are packaged)
oleks added this to the v0.4 — Lint integration & MCP milestone 2026-08-01 15:42:41 +03:00
oleks added the enhancement label 2026-08-01 15:42:41 +03:00
oleks added a new dependency 2026-08-01 15:42:44 +03:00
#1 Add filtering and fleet-wide rollup/summary mode
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
New capability or improvement
No labels enhancement
Milestone
No items
No Milestone v0.4 — Lint integration & MCP
Projects
Clear projects
No projects
Assignees
Clear assignees
oleks
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#1 Add filtering and fleet-wide rollup/summary mode
oleks/pipetree
#4 Annotate pipelines with live run status/history from the Woodpecker API
oleks/pipetree
Reference: oleks/pipetree#7
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?