Inspect CI activity
Browse repositories, pipelines, build logs, agents, and system state.
WOODPECKER CI × MCP
A Woodpecker CI guidance skill backed by a local stdio MCP server.
WHAT IT CAN DO
Browse repositories, pipelines, build logs, agents, and system state.
Use supported read and write operations for Woodpecker CI resources, including secrets.
The MCP server runs on your machine and connects to the Woodpecker API you configure.
GET STARTED
Use Bun 1.1 or newer and a Woodpecker API URL ending in /api.
Install the plugin from the repository.
git clone https://github.com/jurislm/woodpecker-ci-plugin.git
cd woodpecker-ci-plugin
codex plugin marketplace add .
codex plugin add woodpecker-ci@woodpecker-ci-marketplace
Set WOODPECKER_URL and WOODPECKER_API_TOKEN in the MCP server process environment. The macOS Codex app does not inherit interactive shell settings; see the full setup guide below.
Import the plugin from GitHub.
jurislm/woodpecker-ci-plugin and add Woodpecker CI Plugin.For other MCP hosts, run the published package with bun x and set credentials in the MCP server environment. Do not commit credential values.
{
"mcpServers": {
"woodpecker-ci": {
"command": "bun",
"args": ["x", "@jurislm/woodpecker-ci-plugin@latest"],
"env": {
"WOODPECKER_URL": "https://ci.example.com/api",
"WOODPECKER_API_TOKEN": "..."
}
}
}
}
View the npm package
SECURITY & LIMITS
The server sends the token to your configured Woodpecker API as a Bearer token. It does not log the token or include it in MCP tool request metadata. Recognized credential fields in structured JSON responses are replaced with [REDACTED]. Keep credentials out of checked-in files.
/mcp endpointDRONE_TOKEN is not used