Woodpecker

Provides intelligent CI pipeline failure analysis with IDE context and actionable fixes for Woodpecker CI pipelines.

typescript

1

GitHub Stars

typescript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "aman-11-woodpecker-mcp-server": {
      "command": "npx",
      "args": [
        "woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_TOKEN": "your_token",
        "WOODPECKER_SERVER": "https://woodpecker.your-domain.com"
      }
    }
  }
}

You deploy and run an MCP server that analyzes CI pipeline failures, with IDE integration to resolve context from your git workspace. It gives you targeted insights on failing pipelines, highlights root causes, and proposes concrete fixes to improve your CI workflow.

How to use

You can use the MCP server in two practical ways. First, perform direct pipeline analysis when you have specific Woodpecker CI identifiers. Second, perform git-context analysis from your IDE to automatically resolve pipelines using repository name, PR number, or branch information.

How to install

Prerequisites: ensure you have Node.js 18+ and a package manager installed (npm or pnpm). You will also need access to your Woodpecker CI instance or an MCP server URL if you choose to run locally.

Step 1 — Install the MCP client package globally or set up a local project.

Option A: Install globally with npm

npm install -g woodpecker-ci-mcp

Option B: Install locally in your project

npm install woodpecker-ci-mcp

Step 2 — Start the MCP server or configure your client to connect to an MCP endpoint.

If you prefer to run the MCP server via a local build, you can later start it with the appropriate runtime command. The example below demonstrates running the server from a local build path.

node path/to/mcp-pipeline-server/dist/index.js

Additional sections

Configuration: you configure how the MCP server is accessed by your client. Two main approaches exist: a direct, HTTP-based endpoint or a local, stdio-based runtime that you invoke from your environment.

Security: protect your MCP access with tokens and restricted URLs. Store tokens securely and rotate credentials regularly.

Examples and troubleshooting: you will see concrete prompts and outputs showing both human-readable reports and machine-readable JSON to help automate remediation.

Available tools

WoodpeckerCiPipelineReportGeneratorTool

Direct pipeline analysis using repository ID and pipeline number to fetch details and logs for a specific Woodpecker CI pipeline.

GitBasedPipelineAnalyzerTool

IDE-integrated analysis using git context to resolve repository, PR, and branch information, auto-resolve repository ID, and find the latest applicable pipeline.