Skip to content

Woodpecker MCP

Community MCP server for Woodpecker CI — pipelines, logs, repos, secrets management.

Package

mcp-woodpecker — 41+ tools, Woodpecker CI 3.13+ API.

Create a token

Woodpecker accepts Forgejo OAuth or personal access tokens.

Option A — Forgejo token (simplest):

Use the same FORGEJO_API_TOKEN from local/.env if it has sufficient scopes (all recommended for admin tasks).

Option B — Woodpecker-specific token:

  1. Log in to https://ci.rafaelgonzalezalbes.com
  2. Profile → Personal Access Tokens
  3. Add to local/.env:
WOODPECKER_TOKEN=...

Cursor configuration

"woodpecker": {
  "command": "npx",
  "args": ["-y", "mcp-woodpecker"],
  "env": {
    "WOODPECKER_URL": "https://ci.rafaelgonzalezalbes.com",
    "WOODPECKER_API_KEY": "<your-token>"
  }
}

Note: env var is WOODPECKER_API_KEY per the package docs.

Category Examples
Pipelines list pipelines, get pipeline status, get step logs
Repos list repos, search repository
Builds restart pipeline, approve deployment

Typical agent tasks

  • "What's the status of the latest infra/devops pipeline?"
  • "Show logs for the failed test step on bioscancheck"
  • "List recent builds on portfolio main"

Overlap with infra-ops MCP

Use woodpecker MCP for detailed pipeline/log inspection via API.

Use infra-ops MCP for platform-specific scripts (sync to VPS, onboard, health probes).

Troubleshooting

Issue Fix
Empty repo list Token lacks access; regenerate with all scopes
404 on pipeline Check repo slug format: owner/repo (e.g. infra/devops)
Clone failures after private repo Run bash scripts/refresh-woodpecker-forgejo-token.sh on VPS