woodpecker-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port. | 3000 |
| MCP_TRANSPORT | No | Transport mode: stdio or http. The --http flag overrides this setting. | |
| WOODPECKER_URL | Yes | Required. Woodpecker origin only; must be http or https, with no userinfo, query, hash, or path. Example: http://127.0.0.1:8800. | |
| WOODPECKER_TOKEN | No | Required unless WOODPECKER_TOKEN_FILE is set. Woodpecker personal access token, sent as Authorization: Bearer. Redacted in logs, errors, and results. | |
| WOODPECKER_CONTACT | No | Contact token included in the User-Agent. Must not contain the API token. | |
| WOODPECKER_PER_MINUTE | No | Local request budget. Cache hits do not spend it. | 30 |
| WOODPECKER_TIMEOUT_MS | No | Upstream timeout in milliseconds. | 20000 |
| WOODPECKER_TOKEN_FILE | No | Optional. Path to a chmod 600 file whose trimmed contents are the token. Used when WOODPECKER_TOKEN is omitted. | |
| WOODPECKER_ALLOW_WRITES | No | Must be the literal true before a confirmed write is sent. | |
| WOODPECKER_CACHE_TTL_SEC | No | Read cache TTL in seconds. Writes clear the cache. | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| woodpecker_systemB | Current user, version, health, feed, and queue info. Writes run only when confirm is true and WOODPECKER_ALLOW_WRITES=true. Actions: version, health, me, feed, queue_info, pipeline_queue. |
| woodpecker_reposC | Repository list, lookup, get, activate, update, repair, chown, delete, branches, pull requests, permissions, and workflows. Writes run only when confirm is true and WOODPECKER_ALLOW_WRITES=true. Actions: list, list_all, lookup, get, activate, update, repair, chown, delete, branches, pull_requests, permissions, workflows. |
| woodpecker_pipelinesB | Pipeline list, get, trigger, cancel, restart, approve, decline, delete, config, and metadata. Writes run only when confirm is true and WOODPECKER_ALLOW_WRITES=true. Actions: list, get, create, cancel, restart, approve, decline, delete, config, metadata. |
| woodpecker_logsA | Read step logs (base64 decoded to text) and delete step or pipeline logs. Writes run only when confirm is true and WOODPECKER_ALLOW_WRITES=true. Actions: get, delete, delete_pipeline. |
| woodpecker_cronB | Cron list, get, create, update, delete, and run. Writes run only when confirm is true and WOODPECKER_ALLOW_WRITES=true. Actions: list, get, create, update, delete, run. |
| woodpecker_secretsB | Repository, organization, and global secret list, get, create, update, and delete. Secret values are write-only and redacted. Writes run only when confirm is true and WOODPECKER_ALLOW_WRITES=true. Actions: list, get, create, update, delete, org_list, org_get, org_create, org_update, org_delete, global_list, global_get, global_create, global_update, global_delete. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool is scoped to a distinct Woodpecker resource (system, repos, pipelines, logs, cron, secrets), making most selections clear. Minor overlap exists around log/pipeline deletion and queue-related system actions versus pipeline listing, but descriptions provide enough guidance.
All tool names follow a consistent woodpecker_<resource> snake_case convention. Actions within each tool use a predictable verb-style pattern such as list, get, create, update, delete.
Six resource-grouped tools fit the scope well; each groups a coherent set of related operations rather than proliferating one tool per action. The count is appropriate for a CI server MCP surface.
Core CI lifecycle coverage is strong: repositories, pipelines, logs, cron, secrets, and system health are all represented. Some peripheral Woodpecker areas such as agents, registries, webhooks, or broader user/org administration appear absent but are not central to most workflows.