mcpbeat Sign in

Woodpecker CI MCP Server

local only

Woodpecker CI runs on your own machine — the client starts it, so there is no endpoint to ping. 45 installs a week from npm. Last commit 15 Oct 2026.

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

Installs per day peak 19 · avg 7 · -9% w/w
a month agotoday
45
Installs / week
npm · @ni-c/woodpecker-ci-mcp
0
Stars
0 open issues
15 Oct 2026
Last commit
3 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 19 h ago · rules ccca72095570

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Reaches cloud metadata service src/hosts.ts:16
  'metadata.google.internal',

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Woodpecker CI and you get told the day something new turns up.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add woodpecker-ci-mcp -- npx -y @ni-c/woodpecker-ci-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "woodpecker-ci-mcp": {
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.woodpecker-ci-mcp]
command = "npx"
args = ["-y", "@ni-c/woodpecker-ci-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "woodpecker-ci-mcp": {
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "woodpecker-ci-mcp": {
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: WOODPECKER_URL (Root URL of the Woodpecker server, e.g. https://woodpecker.example.com), WOODPECKER_TOKEN (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)), WOODPECKER_API_PREFIX (Path of the API below the server root (default: /api; Crow CI 5 and later: /api/v1)). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Woodpecker CI

same job, measured the same way
Drone CI/CD MCP Server
by yusiwen

MCP server for Drone CI/CD: 45 tools for builds, repos, secrets, users and templates

local only
Bitbucket MCP Server
by lawp09

MCP server for Bitbucket API - manage repositories, pull requests, comments, pipelines and more

1 445 installs/wk local only
Repo-to-RAG
by evozim

GitHub repository vectorizer and context synthesizer for RAG pipelines.

answering
Repo Release Tools
by anselmoo

Config-driven branch and release helpers for Git repositories

319 installs/wk local only
Laserfiche MCP
by adventist-gc

MCP server for self-hosted Laserfiche repositories — search and read documents from Claude.

832 installs/wk local only
Laserfiche MCP
by samuelshernandez

MCP server for self-hosted Laserfiche repositories — search and read documents from Claude.

local only
Project Brain
by gentleelephant

Read-only source search and retrieval across configured GitHub repositories

local only
V
VillApps
by villapps

Desktop app with a local MCP server: your coding AI builds business screens, reports and charts.

local only

Woodpecker CI — questions

Answers built from our own checks of this server.

Why is there no uptime for Woodpecker CI?
Woodpecker CI runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @ni-c/woodpecker-ci-mcp was installed 45 times last week.
How do I connect Woodpecker CI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @ni-c/woodpecker-ci-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Woodpecker CI?
The npm package @ni-c/woodpecker-ci-mcp was installed 45 times in the last week. Week over week that is -9%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Woodpecker CI open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.