Woodpecker CI MCP Server

by ni-cio.github.ni-c/woodpecker-ci-mcpv0.3.1

Drive a self-hosted Woodpecker CI: read failing step logs, restart, cancel or approve pipelines, and manage secrets, registries, crons, agents and the queue.

0Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active2d ago

Install Woodpecker CI MCP server

claude mcp add woodpecker-ci -e WOODPECKER_URL='<woodpecker-url>' -e WOODPECKER_TOKEN='<woodpecker-token>' -- npx -y @ni-c/woodpecker-ci-mcp

{
  "mcpServers": {
    "woodpecker-ci": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_URL": "<woodpecker-url>",
        "WOODPECKER_TOKEN": "<woodpecker-token>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

{
  "mcpServers": {
    "woodpecker-ci": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_URL": "<woodpecker-url>",
        "WOODPECKER_TOKEN": "<woodpecker-token>"
      }
    }
  }
}

Settings → Developer → Edit Config (claude_desktop_config.json), then restart.

{
  "servers": {
    "woodpecker-ci": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_URL": "<woodpecker-url>",
        "WOODPECKER_TOKEN": "<woodpecker-token>"
      }
    }
  }
}

Add to .vscode/mcp.json in your workspace.

{
  "mcpServers": {
    "woodpecker-ci": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_URL": "<woodpecker-url>",
        "WOODPECKER_TOKEN": "<woodpecker-token>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

Configuration

Variable	Required	Secret	Description
WOODPECKER_URL	yes	—	Root URL of the Woodpecker server, e.g. https://woodpecker.example.com
WOODPECKER_TOKEN	yes	yes	Personal access token from the Woodpecker user settings
WOODPECKER_READ_ONLY	—	—	Set to true to register only the read tools (default: false)
WOODPECKER_ALLOW_TOOLS	—	—	Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
WOODPECKER_DENY_TOOLS	—	—	Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
WOODPECKER_INSECURE_TLS	—	—	Set to true to accept a self-signed certificate from the Woodpecker server (default: false)

Freshness

Active — last maintenance signal 2d ago. The newest of the signals below sets the band.

Last commit (default branch)
2026-10-08 · 2d ago · GitHub
Latest release
2026-09-07 · 33d ago · GitHub · v0.3.1
Package published
no data · npm/PyPI
Registry entry updated
2026-09-07 · 33d ago · official registry · v0.3.1

FAQ

›How do I install the Woodpecker CI MCP server in Claude Code?

Run: claude mcp add woodpecker-ci -e WOODPECKER_URL='<woodpecker-url>' -e WOODPECKER_TOKEN='<woodpecker-token>' -- npx -y @ni-c/woodpecker-ci-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Woodpecker CI require an API key?

Yes. It expects WOODPECKER_URL, WOODPECKER_TOKEN, of which 1 is a secret.

›Can I use Woodpecker CI as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Woodpecker CI in the official MCP registry?

Yes, as io.github.ni-c/woodpecker-ci-mcp.