Compatible with every major AI agent and IDE
What is the Woodpecker CI MCP Server?
Connect your Woodpecker CI server to any AI agent to automate your continuous integration and deployment workflows through natural language.
What you can do
- Pipeline Control — List, trigger, restart, or cancel pipelines for any repository to keep your builds moving.
- Agent Monitoring — View all connected agents, check their health metrics, and manage task assignments in real-time.
- Repository Management — Activate new repositories, update settings, and repair webhooks without leaving your chat interface.
- Secret & Config Management — Securely handle global, organization, or repository-level secrets and inspect pipeline configurations.
- System Insights — Retrieve server version, health status, and performance metrics to ensure your CI infrastructure is running smoothly.
How it works
- Subscribe to this server
- Provide your Woodpecker Server URL and Personal Access Token
- Start orchestrating your DevOps workflows from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — Monitor build agents and troubleshoot failing pipelines using simple queries.
- Software Developers — Trigger builds and check pipeline status directly from the code editor.
- SREs & System Admins — Keep an eye on CI infrastructure health and manage secrets across the organization.
Built-in capabilities (34)
Activate a repository
Cancel a running pipeline
Change repository owner to the current user
Create a new Woodpecker agent
Create a global secret
Create a repository secret
Delete an agent
Delete a pipeline
Deactivate/delete a repository
Get details of a specific agent
Server health check
Prometheus metrics (requires WOODPECKER_PROMETHEUS_AUTH_TOKEN if configured)
Get user permissions for an organization
Get details of a specific pipeline
Get the configuration files used for a pipeline
Get repository details
Get the currently authenticated user
Get server version information
List tasks currently assigned to an agent
List all Woodpecker agents
List global secrets (Admin only)
List agents scoped to an organization
List organization-level secrets
List all organizations
List pipelines for a repository
List repository-level secrets
List all repositories on the server
List all users (Admin only)
Lookup a repository by its full name (slug)
Repair repository webhooks
Restart a pipeline
Trigger a manual pipeline
Update an existing agent
Update repository settings
Why Claude Code?
Claude Code registers Woodpecker CI as an MCP server in a single terminal command. Once connected, Claude Code discovers all 34 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Woodpecker CI data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Woodpecker CI tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Woodpecker CI in Claude Code
Woodpecker CI and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Woodpecker CI to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Woodpecker CI in Claude Code
The Woodpecker CI MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 34 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Woodpecker CI for Claude Code
Every tool call from Claude Code to the Woodpecker CI MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I trigger a new pipeline build for a specific repository?
Yes. Use the trigger_pipeline tool by providing the repository ID. You can also specify a branch or commit if needed to start a new execution immediately.
How do I check if my build agents are online and healthy?
You can use list_agents to see all connected agents and their status. For more detail on a specific agent, use get_agent or list_agent_tasks to see what it's currently working on.
Is it possible to manage environment secrets through this agent?
Yes, the server includes tools like create_repo_secret and list_repo_secrets to manage sensitive variables at the repository level, as well as global and organization-level secret tools.
How do I add an MCP server to Claude Code?
Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
Explore More MCP Servers
View all →
Bright Pattern
10 toolsOrchestrate your contact center via Bright Pattern — manage users, track interactions, and monitor real-time stats directly from any AI agent.

Aviationstack
9 toolsGlobal aviation data platform — track real-time flights, airports, and airline data via AI.

LegiScan Legislation Lookup
3 toolsUniversal legislative intelligence — search bills, votes, and state laws via AI.

Pointr
10 toolsGrant your AI access to precision indoor mapping. Navigate buildings, track BLE beacons, and find POIs.
