Repository navigation
Releases: RikiGomes/woodpecker-mcp
Releases · RikiGomes/woodpecker-mcp
Release list
v0.2.0
Two new read-only capabilities for triaging a red pipeline.
Install pinned to this release: github:RikiGomes/woodpecker-mcp#v0.2.0
New
compare_pipelines: answers "what broke?" in one call. On a branch it finds the newest failing run and the last green one before it (or takes explicitbad/goodnumbers) and returns both summaries, the runs in between, only the steps whose state changed, the names of config files that changed, and the failing step ids forget_step_logs. Pull request runs are left out by default, since Woodpecker files them under their target branch;eventchanges that.list_secretsscopes:scope: "org"lists the repository's organization secrets andscope: "global"the server-wide ones, alongside the existing repository scope. Names, events, images and notes only; values are never returned.
Fixes
- The smoke test checks the configured instance URL exactly (code scanning alert).
Still read-only: GET requests only, every tool marked readOnlyHint. Requires Node 20.12 or newer.
v0.1.0
First tagged release of woodpecker-mcp, a read-only MCP server for Woodpecker CI.
Install pinned to this release:
{
"mcpServers": {
"woodpecker": {
"command": "npx",
"args": ["-y", "github:RikiGomes/woodpecker-mcp#v0.1.0"],
"env": {
"WOODPECKER_URL": "https://ci.example.com",
"WOODPECKER_TOKEN": "${WOODPECKER_TOKEN}"
}
}
}
}What's in it
- 14 read-only tools: pipelines, step logs (tail or search), pipeline diagnosis, config, branches, pull requests, crons, secret names, agents, queue info and recent activity, across one or more Woodpecker instances.
- Read-only by contract: GET requests only, every tool marked
readOnlyHint. Secret values, cron variable values and agent tokens are never returned. - Lean responses to save tokens: compact JSON, ANSI and spinner noise stripped from logs, repeated lines collapsed, passing steps counted instead of listed.
- Hardening: the token stays in the Authorization header and is redacted from relayed errors; repo slugs are validated against path traversal;
.env.woodpeckercannot redirect a token from your environment; URLs with credentials or non-http(s) schemes are rejected; response bodies and tool output are size-capped.
Requirements
Node 20.12 or newer. Tested on Node 20.12, 22 and 24.
Logs, commit messages and pipeline YAML are written by whoever pushes to a repo; treat them as untrusted data. Report vulnerabilities privately, see SECURITY.md.