Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons
To add Woodpecker CI to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 7 environment variables, listed below.
Install
npx -y @ni-c/woodpecker-ci-mcp@0.4.0Environment variables
WOODPECKER_URLSet in your MCP configWOODPECKER_TOKENSet in your MCP configWOODPECKER_READ_ONLYSet in your MCP configWOODPECKER_ALLOW_TOOLSSet in your MCP configWOODPECKER_DENY_TOOLSSet in your MCP configWOODPECKER_INSECURE_TLSSet in your MCP configWOODPECKER_API_PREFIXSet in your MCP configInstall with your client
claude mcp add woodpecker-ci --env WOODPECKER_URL=<YOUR_WOODPECKER_URL> --env WOODPECKER_TOKEN=<YOUR_WOODPECKER_TOKEN> --env WOODPECKER_READ_ONLY=<YOUR_WOODPECKER_READ_ONLY> --env WOODPECKER_ALLOW_TOOLS=<YOUR_WOODPECKER_ALLOW_TOOLS> --env WOODPECKER_DENY_TOOLS=<YOUR_WOODPECKER_DENY_TOOLS> --env WOODPECKER_INSECURE_TLS=<YOUR_WOODPECKER_INSECURE_TLS> --env WOODPECKER_API_PREFIX=<YOUR_WOODPECKER_API_PREFIX> -- npx -y @ni-c/woodpecker-ci-mcp@0.4.0
Run this in a terminal to add the server to Claude Code.
What this does
Woodpecker CI exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server needs the following environment variables to be set before it can run:
WOODPECKER_URL WOODPECKER_TOKEN WOODPECKER_READ_ONLY WOODPECKER_ALLOW_TOOLS WOODPECKER_DENY_TOOLS WOODPECKER_INSECURE_TLS WOODPECKER_API_PREFIX
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install Woodpecker CI?
Run the Claude Code command in the install section to add Woodpecker CI to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with Woodpecker CI?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Woodpecker CI as well.
Does Woodpecker CI need an API key?
Yes. Before it can run, set these environment variables: WOODPECKER_URL, WOODPECKER_TOKEN, WOODPECKER_READ_ONLY, WOODPECKER_ALLOW_TOOLS, WOODPECKER_DENY_TOOLS, WOODPECKER_INSECURE_TLS, WOODPECKER_API_PREFIX. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-ni-c-woodpecker-ci-mcp)<a href="https://clauderules.net/mcp/io-github-ni-c-woodpecker-ci-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-ni-c-woodpecker-ci-mcp" alt="Listed on clauderules.net" /></a>More Files MCP servers
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
eyaltoledano/claude-task-master
📇 ☁️ 🏠 - AI-powered task management system for AI-driven development. Features PRD parsing, task expansion, multi-provider support (Claude, OpenAI, Gemini, Perplexity, xAI), and selective tool loadi
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.