Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons
Connect Runs on your machine
claude mcp add woodpecker-ci-mcp -e WOODPECKER_URL=<WOODPECKER_URL> -e WOODPECKER_TOKEN=<WOODPECKER_TOKEN> -e WOODPECKER_READ_ONLY=<WOODPECKER_READ_ONLY> -e WOODPECKER_ALLOW_TOOLS=<WOODPECKER_ALLOW_TOOLS> -e WOODPECKER_DENY_TOOLS=<WOODPECKER_DENY_TOOLS> -e WOODPECKER_INSECURE_TLS=<WOODPECKER_INSECURE_TLS> -e WOODPECKER_API_PREFIX=<WOODPECKER_API_PREFIX> -- npx -y @ni-c/[email protected]
{
"mcpServers": {
"woodpecker-ci-mcp": {
"command": "npx",
"args": [
"-y",
"@ni-c/[email protected]"
],
"env": {
"WOODPECKER_URL": "<WOODPECKER_URL>",
"WOODPECKER_TOKEN": "<WOODPECKER_TOKEN>",
"WOODPECKER_READ_ONLY": "<WOODPECKER_READ_ONLY>",
"WOODPECKER_ALLOW_TOOLS": "<WOODPECKER_ALLOW_TOOLS>",
"WOODPECKER_DENY_TOOLS": "<WOODPECKER_DENY_TOOLS>",
"WOODPECKER_INSECURE_TLS": "<WOODPECKER_INSECURE_TLS>",
"WOODPECKER_API_PREFIX": "<WOODPECKER_API_PREFIX>"
}
}
}
}
{
"mcpServers": {
"woodpecker-ci-mcp": {
"command": "npx",
"args": [
"-y",
"@ni-c/[email protected]"
],
"env": {
"WOODPECKER_URL": "<WOODPECKER_URL>",
"WOODPECKER_TOKEN": "<WOODPECKER_TOKEN>",
"WOODPECKER_READ_ONLY": "<WOODPECKER_READ_ONLY>",
"WOODPECKER_ALLOW_TOOLS": "<WOODPECKER_ALLOW_TOOLS>",
"WOODPECKER_DENY_TOOLS": "<WOODPECKER_DENY_TOOLS>",
"WOODPECKER_INSECURE_TLS": "<WOODPECKER_INSECURE_TLS>",
"WOODPECKER_API_PREFIX": "<WOODPECKER_API_PREFIX>"
}
}
}
}
{
"servers": {
"woodpecker-ci-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ni-c/[email protected]"
],
"env": {
"WOODPECKER_URL": "<WOODPECKER_URL>",
"WOODPECKER_TOKEN": "<WOODPECKER_TOKEN>",
"WOODPECKER_READ_ONLY": "<WOODPECKER_READ_ONLY>",
"WOODPECKER_ALLOW_TOOLS": "<WOODPECKER_ALLOW_TOOLS>",
"WOODPECKER_DENY_TOOLS": "<WOODPECKER_DENY_TOOLS>",
"WOODPECKER_INSECURE_TLS": "<WOODPECKER_INSECURE_TLS>",
"WOODPECKER_API_PREFIX": "<WOODPECKER_API_PREFIX>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
WOODPECKER_URLRequired | Root URL of the Woodpecker server, e.g. https://woodpecker.example.com |
WOODPECKER_TOKENRequired, secret | Personal access token from the Woodpecker user settings |
WOODPECKER_READ_ONLYOptional | Set to true to register only the read tools (default: false) |
WOODPECKER_ALLOW_TOOLSOptional | Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools) |
WOODPECKER_DENY_TOOLSOptional | Comma-separated tool names or list_* prefixes to remove from whatever the allow list left |
WOODPECKER_INSECURE_TLSOptional | Set to true to accept a self-signed certificate from the Woodpecker server (default: false) |
WOODPECKER_API_PREFIXOptional | Path of the API below the server root (default: /api; Crow CI 5 and later: /api/v1) |
Details
| Package | @ni-c/[email protected] (NPM, stdio) |
| Package | ghcr.io/ni-c/woodpecker-ci-mcp:0.4.0 (OCI, stdio) |
| First published | 15 Oct 2026 |
| Last updated | 15 Oct 2026 |
| Registry name | io.github.ni-c/woodpecker-ci-mcp |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
