Developer · Local MCP server
Woodpecker CI
Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ni-c/woodpecker-ci-mcp- Version
- 0.3.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm, OCI image (Docker)
- Published
- 2026-09-07
- Updated
- 2026-09-07
- Publisher
- ni-c (GitHub) · 18 servers with pages here
- Website
- woodpecker-ci-mcp.ni-c.de
- Repository
- github.com/ni-c/woodpecker-ci-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @ni-c/woodpecker-ci-mcp | 0.3.1 | stdio |
| OCI image (Docker) | ghcr.io/ni-c/woodpecker-ci-mcp:0.3.1 | — | stdio |
How to connect Woodpecker CI
Woodpecker CI runs locally from a Node.js package published to the npm registry: @ni-c/woodpecker-ci-mcp version 0.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @ni-c/woodpecker-ci-mcp@0.3.1. It reads these environment variables: WOODPECKER_URL (required), WOODPECKER_TOKEN (required, secret), WOODPECKER_READ_ONLY, WOODPECKER_ALLOW_TOOLS, WOODPECKER_DENY_TOOLS and WOODPECKER_INSECURE_TLS; set them in the client's configuration for this server.
Woodpecker CI runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/ni-c/woodpecker-ci-mcp:0.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e WOODPECKER_URL -e WOODPECKER_TOKEN -e WOODPECKER_READ_ONLY -e WOODPECKER_ALLOW_TOOLS -e WOODPECKER_DENY_TOOLS -e WOODPECKER_INSECURE_TLS ghcr.io/ni-c/woodpecker-ci-mcp:0.3.1. It reads these environment variables: WOODPECKER_URL (required), WOODPECKER_TOKEN (required, secret), WOODPECKER_READ_ONLY, WOODPECKER_ALLOW_TOOLS, WOODPECKER_DENY_TOOLS and WOODPECKER_INSECURE_TLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"woodpecker-ci-mcp": {
"command": "npx",
"args": [
"-y",
"@ni-c/woodpecker-ci-mcp@0.3.1"
],
"env": {
"WOODPECKER_URL": "<value>",
"WOODPECKER_TOKEN": "<secret>",
"WOODPECKER_READ_ONLY": "<value>",
"WOODPECKER_ALLOW_TOOLS": "<value>",
"WOODPECKER_DENY_TOOLS": "<value>",
"WOODPECKER_INSECURE_TLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from ni-c (GitHub)
| Server | Runs |
|---|---|
| HealthchecksInspect, create and adjust Healthchecks cron and uptime checks, and read why one failed. | Local · stdio |
| Hetzner DNSManage DNS zones and records (zonefiles, RRSets, TTL, protection) via the Hetzner Cloud API. | Local · stdio |
| IMAP mailboxRead, search and organise any IMAP mailbox, with writes off by default. | Local · stdio |
| LinkwardenMCP server for Linkwarden, the self-hosted bookmark manager with page preservation. | Local · stdio |
| mcp-hubMany stdio MCP servers from one container, published over HTTPS with OAuth 2.1 for any MCP client. | Local · stdio, HTTP |
| Mealie MCP ServerMCP server for Mealie, the self-hosted recipe manager and meal planner. | Local · stdio |
| ntfyPublish ntfy notifications, read the message cache, and manage users and topic access. | Local · stdio |
| OpengistRead, create, update and delete gists on a self-hosted Opengist instance. | Local · stdio |
| OpenStreetMapGeocoding, walking/driving/cycling distances, route optimization, isochrones and POI search on OSM. | Local · stdio |
| SMTPMCP server that sends mail over SMTP, gated behind an allowlist and a human confirmation. | Local · stdio |
| wg-easyAdminister wg-easy (WireGuard Easy) v15: manage VPN clients, configs, QR codes and server status. | Local · stdio |
| Wiki.jsSearch, read and edit Wiki.js pages, and manage its assets, users, groups and comments. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Wisp MCPWisp Panel MCP server for secure game server management through the Wisp Client API. | Local · stdio |
| WjttcF1-grade MCP certification. 52 tests, 9 tiers (49 scored + T9 Receipt validation). Ecosystem: #2759. | Local · stdio |
| Wokelo MCP ServerCompany and market intelligence, news, enrichment, and agentic workflows for dealmakers. | Remote · HTTP |
| wontopos.comWontopos (WOS) long-term memory (beta) - one memory across Claude Code, Cursor, and your agents. | Local · stdio |
| Wopee MCPAI testing agents for web apps — dispatch test runs, crawls, fetch artifacts and status. | Local · stdio |
| WordMicrosoft Word automation for AI assistants. Requires Word for Windows. | Local · stdio |
| Word Cloud Generator (word-cloud.net)Generate word clouds from text with custom fonts, colors, backgrounds, gradients, and shape masks. | Remote · HTTP |
| Word MCP Server (FsWordDsl)Word tools for AI agents: read/write, decompile to F#/C#/XML/JSON, or build from XML/JSON. | Local · stdio |