git-based-pipeline-analyzer
Analyzes CI pipeline failures using git context from IDE. Can auto-resolve repository and pipeline details from git information like repo name, PR number, or branch name.
LABSCO SUMMARY
From "the pipeline failed" to "this file, this line".
The useful part is not fetching the logs — it is that the pipeline is found from the branch or PR you are already on, and only the final attempt of each step is read. What comes back is a report organised by file rather than a wall of CI output.
What it is
An MCP server for Woodpecker CI failure analysis, with two ways in: a pipeline named directly by repository id and number, or one resolved from the git context your IDE already has.
What you get
- Machine logs extracted for a given pipeline, pulled per step rather than as one undifferentiated stream
- Pipelines resolved from git context — repository name, PR number or branch — so a URL does not have to be found first
- The repository id resolved from its name, and the latest pipeline for a pull request located automatically
- Only the final attempt of a retried step analysed, so a flaky retry does not double the noise
- A structured report as Markdown and JSON, with fix suggestions organised file by file
- Two prompts shipped with it: one for direct repo-and-pipeline analysis, one for PR failures from the IDE
- Running pipelines handled without erroring out
Requirements
Two environment variables: WOODPECKER_SERVER for your Woodpecker instance and WOODPECKER_TOKEN for the account it reads as. The git-context path additionally assumes it is running where your repository is checked out.
Setup effort
One command plus a key — npm install -g woodpecker-ci-mcp, then supply credentials
USE CASES
01
Finding out why your PR is red
The pipeline for the branch or pull request you are on is resolved from git context, so the analysis starts without hunting for a CI URL.
02
Analysing a specific run someone sent you
Give the repository id and pipeline number from the Woodpecker URL and pull that run's step logs directly.
03
Reading a long CI log without reading all of it
Logs come back per step and only for final attempts, so a retried flaky step does not bury the real failure.
04
Turning a failure into a list of edits
The report is organised file by file with suggested fixes, which is the form you can act on in the editor.
05
Checking a pipeline that is still running
In-flight pipelines are handled rather than treated as an error, so the question can be asked before the run finishes.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
woodpecker-ci-pipeline-report-generator
This tool is used to extract all the different machine logs for the given pipeline
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
- npx on PATH
- Node.js 18+
- WOODPECKER_SERVER in your environment
- WOODPECKER_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"woodpecker-ci": {
"command": "npx",
"args": [
"woodpecker-ci-mcp"
],
"env": {
"WOODPECKER_SERVER": "<YOUR_WOODPECKER_SERVER>",
"WOODPECKER_TOKEN": "<YOUR_WOODPECKER_TOKEN>"
}
}
}
}npm
TERMINAL
npm install -g woodpecker-ci-mcp
