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 Cursor?
Cursor's Agent mode turns Woodpecker CI into an in-editor superpower. Ask Cursor to generate code using live data from Woodpecker CI and it fetches, processes, and writes. all in a single agentic loop. 34 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Woodpecker CI in Cursor
Woodpecker CI and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Woodpecker CI to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Telnyx
10 toolsSend and manage SMS/MMS, check account balances, and configure messaging profiles natively via your AI agent.

Nuvei
10 toolsConnect your AI agent to Nuvei to track transactions, manage payments, and securely tokenize cards through natural conversation.

Comet ML
6 toolsManage machine learning experiments via Comet — track model metrics, audit project workspaces, and inspect ML run parameters directly from any AI agent.

EasyPost
10 toolsEquip your AI agent to manage shipments, track packages, and monitor carrier accounts via the EasyPost API.
