Woodpecker CI MCP Server

Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons

Local serverstdio

What is the Woodpecker CI MCP Server?

Woodpecker CI is an MCP integration. Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons.

Packages and local setup

The published npm package is @ni-c/woodpecker-ci-mcp, version 0.3.1. Its declared MCP transport is stdio.

The package declares WOODPECKER_URL (required): Root URL of the Woodpecker server, e.g. https://woodpecker.example.com; WOODPECKER_TOKEN (required): 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).

The published oci package is ghcr.io/ni-c/woodpecker-ci-mcp:0.3.1. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.3.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
WOODPECKER_URLRoot URL of the Woodpecker server, e.g. https://woodpecker.example.comYes
WOODPECKER_TOKENPersonal access token from the Woodpecker user settingsYes
WOODPECKER_READ_ONLYSet to true to register only the read tools (default: false)Optional
WOODPECKER_ALLOW_TOOLSComma-separated tool names or list_ prefixes to register; 'essential' selects a curated preset (default: all tools)Optional
WOODPECKER_DENY_TOOLSComma-separated tool names or list_ prefixes to remove from whatever the allow list leftOptional
WOODPECKER_INSECURE_TLSSet to true to accept a self-signed certificate from the Woodpecker server (default: false)Optional