MCP Tools DirectoryAbout this integration
Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.3.1
- Package
- @ni-c/woodpecker-ci-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@ni-c/woodpecker-ci-mcpPublisher README and npm manifest reviewed from pinned captures. Package and Woodpecker endpoint were not executed; documented permission and human-approval boundaries remain applicable.
Capabilities: Inspect repositories, pipelines, and build logs, Trigger, restart, cancel, and approve pipelines, Manage secrets, registries, and cron schedules, Administer Woodpecker accounts, agents, forges, and queue state
Connected profiles
Additional details
io.github.ni-c/woodpecker-ci-mcp
Source ↗ · Checked 2026-09-170.3.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17WOODPECKER_URL, WOODPECKER_TOKEN
Source ↗ · Checked 2026-09-17@ni-c/woodpecker-ci-mcp
Source ↗ · Checked 2026-09-190.3.1
Source ↗ · Checked 2026-09-19Publisher documents a stdio MCP process launched by npx or Docker, with optional read-only and tool allow/deny modes; guarded operations can require person approval.
Source ↗ · Checked 2026-09-19The server requires a Woodpecker personal access token carrying the authority of its user account.
Source ↗ · Checked 2026-09-19The documented connection launches npx -y @ni-c/woodpecker-ci-mcp with WOODPECKER_URL and WOODPECKER_TOKEN.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19