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 VS Code Copilot?
GitHub Copilot Agent mode brings Woodpecker CI data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 34 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Woodpecker CI in VS Code Copilot
Woodpecker CI and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Woodpecker CI to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Leadfeeder
9 toolsBring Leadfeeder B2B visit intelligence to your AI. Discover which companies visit your website natively.

DoorDash Drive
10 toolsEquip your AI agent to manage deliveries, track dashers, and monitor order status via the DoorDash Drive API.

Volcengine Speech Synthesis
7 toolsThe massive 'TikTok Voice' TTS API — generate natural speech with ByteDance's iconic voice models.

Papermark (Docsend Alternative)
6 toolsSecurely share documents, track engagement, and manage links with Papermark — the open-source DocSend alternative for your AI agent.
