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
We read the source, 19 h ago · rules ccca72095570
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.
'metadata.google.internal',
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
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.
claude mcp add woodpecker-ci-mcp -- npx -y @ni-c/woodpecker-ci-mcp
{
"mcpServers": {
"woodpecker-ci-mcp": {
"args": [
"-y",
"@ni-c/woodpecker-ci-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.woodpecker-ci-mcp]
command = "npx"
args = ["-y", "@ni-c/woodpecker-ci-mcp"]
{
"mcpServers": {
"woodpecker-ci-mcp": {
"args": [
"-y",
"@ni-c/woodpecker-ci-mcp"
],
"command": "npx"
}
}
}
{
"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.
MCP server for Drone CI/CD: 45 tools for builds, repos, secrets, users and templates
MCP server for Bitbucket API - manage repositories, pull requests, comments, pipelines and more
GitHub repository vectorizer and context synthesizer for RAG pipelines.
Config-driven branch and release helpers for Git repositories
MCP server for self-hosted Laserfiche repositories — search and read documents from Claude.
MCP server for self-hosted Laserfiche repositories — search and read documents from Claude.
Read-only source search and retrieval across configured GitHub repositories
Desktop app with a local MCP server: your coding AI builds business screens, reports and charts.
Answers built from our own checks of this server.