Woodpecker CI MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Woodpecker CI MCP ServerWhy did pipeline #42 fail for owner/repo?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Woodpecker CI MCP Server
A Model Context Protocol (MCP) server that connects AI assistants to Woodpecker CI. Debug pipeline failures, analyze build logs, troubleshoot CI/CD configurations, and act on pipelines and repositories (trigger, restart, cancel, approve/decline, activate, update settings) with AI assistance.
MCP Client Setup
Add to your MCP client configuration:
Standalone Binary
{
"woodpecker-ci": {
"command": "woodpecker-mcp",
"env": {
"WOODPECKER_TOKEN": "your-token-here",
"WOODPECKER_URL": "https://your-woodpecker-instance.com"
}
}
}Docker
{
"woodpecker-ci": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e", "WOODPECKER_TOKEN",
"-e", "WOODPECKER_URL",
"ghcr.io/j04n-f/woodpecker-mcp"
],
"env": {
"WOODPECKER_TOKEN": "your-token-here",
"WOODPECKER_URL": "https://your-woodpecker-instance.com"
}
}
}Related MCP server: GoCD MCP Server
Quick Start
Install dependencies
bun installRun the server
# Development with inspector bun run devSet environment variables using Inspector
WOODPECKER_URL="https://your-woodpecker-instance.com" WOODPECKER_TOKEN="your-personal-access-token"Start development environment
# Start Gitea + Woodpecker CI for testing ./scripts/setup-environment.sh # Access services: # - Gitea: http://localhost:3000 (woodpecker/woodpecker123) # - Woodpecker: http://localhost:8000
Configuration
Getting Your Woodpecker Token
Go to your Woodpecker CI instance
Click your profile icon → "CLI & API"
Copy the personal access token
Set it as
WOODPECKER_TOKEN
API Reference
Tool | Description | Parameters |
| Find repository by name |
|
| List all repositories | Optional: |
| Get repository details |
|
| Activate a repository |
|
| Update repository settings |
|
| Repair a repository's webhook |
|
| List repository pipelines |
|
| Get detailed pipeline info |
|
| View pipeline configuration |
|
| Trigger a manual pipeline |
|
| Restart a pipeline |
|
| Cancel a running pipeline |
|
| Approve a pipeline awaiting approval |
|
| Decline a pipeline awaiting approval |
|
| Get logs for debugging |
|
AI Prompts
Prompt | Description |
| Systematic analysis of pipeline failures |
Development
Available Commands
# Development
bun run dev # Start with inspector
bun run build # Build production binary
# Code Quality
bun run lint # Check code style
bun run lint:fix # Auto-fix issuesLocal Testing Environment
The included Docker Compose setup provides:
Gitea: Git forge with webhooks
Woodpecker CI: Complete CI/CD environment
Test repository: Sample project with pipeline configuration
Perfect for testing MCP integration without external dependencies.
Examples
Debug a Failed Pipeline
AI: Can you check why pipeline #42 failed for repository owner/project?Analyze Build Performance
AI: Show me the recent pipeline performance for my main repository and identify any bottlenecks.Configuration Review
AI: Review the pipeline configuration for repository owner/project and suggest improvements.Contributing
Fork the repository
Create a feature branch:
git checkout -b feature/amazing-featureFollow the coding standards:
bun run lintCommit changes:
git commit -m 'feat: add amazing feature'Submit a Pull Request
License
MIT License - see LICENSE for details.
Ready to supercharge your Woodpecker CI workflows with AI assistance! 🚀🤖
This server cannot be deployed
Maintenance
Related MCP Connectors
Agentic CI operations for build inspection, failure diagnosis, and runner troubleshooting.
The Buildkite MCP server exposes Buildkite product data (pipelines, builds, jobs, and test data) to AI tools, editors, and agents through the Model Context Protocol. It provides capabilities including pipeline creation and management, build monitoring with specialized tools like 'wait_for_build', efficient log querying using Apache Parquet conversion and caching, and OAuth-based authentication for both read-write and read-only access to Buildkite's REST API.
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.…
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceIntegrates GitLab with AI assistants to manage merge requests, analyze CI/CD pipelines, and create Architecture Decision Records. It enables seamless code searching, pipeline triggering, and deployment management through the Model Context Protocol.1MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to query and manage GoCD pipelines, stages, and jobs through the Model Context Protocol. It allows users to trigger builds, analyze failures, and access build logs or artifacts using the GoCD REST API.31 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with GitHub repositories, issues, pull requests, and content via the Model Context Protocol.1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Azure DevOps, providing tools for managing work items, repositories, pipelines, and more through the Model Context Protocol.1005 npmMIT