4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
Woodpecker CI MCP Server

Bring Ci Cd
to Claude Desktop

Learn how to connect Woodpecker CI to Claude Desktop and start using 34 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Activate RepoCancel PipelineChown RepoCreate AgentCreate Global SecretCreate Repo SecretDelete AgentDelete PipelineDelete RepoGet AgentGet HealthzGet MetricsGet Org PermissionsGet PipelineGet Pipeline ConfigGet RepoGet UserGet VersionList Agent TasksList AgentsList Global SecretsList Org AgentsList Org SecretsList OrgsList PipelinesList Repo SecretsList ReposList UsersLookup RepoRepair RepoRestart PipelineTrigger PipelineUpdate AgentUpdate Repo

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Woodpecker CI

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

  1. Subscribe to this server
  2. Provide your Woodpecker Server URL and Personal Access Token
  3. 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_repo

Activate a repository

cancel_pipeline

Cancel a running pipeline

chown_repo

Change repository owner to the current user

create_agent

Create a new Woodpecker agent

create_global_secret

Create a global secret

create_repo_secret

Create a repository secret

delete_agent

Delete an agent

delete_pipeline

Delete a pipeline

delete_repo

Deactivate/delete a repository

get_agent

Get details of a specific agent

get_healthz

Server health check

get_metrics

Prometheus metrics (requires WOODPECKER_PROMETHEUS_AUTH_TOKEN if configured)

get_org_permissions

Get user permissions for an organization

get_pipeline

Get details of a specific pipeline

get_pipeline_config

Get the configuration files used for a pipeline

get_repo

Get repository details

get_user

Get the currently authenticated user

get_version

Get server version information

list_agent_tasks

List tasks currently assigned to an agent

list_agents

List all Woodpecker agents

list_global_secrets

List global secrets (Admin only)

list_org_agents

List agents scoped to an organization

list_org_secrets

List organization-level secrets

list_orgs

List all organizations

list_pipelines

List pipelines for a repository

list_repo_secrets

List repository-level secrets

list_repos

List all repositories on the server

list_users

List all users (Admin only)

lookup_repo

Lookup a repository by its full name (slug)

repair_repo

Repair repository webhooks

restart_pipeline

Restart a pipeline

trigger_pipeline

Trigger a manual pipeline

update_agent

Update an existing agent

update_repo

Update repository settings

Why Claude Desktop?

Claude Desktop is the definitive way to connect Woodpecker CI to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 34 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

Woodpecker CI in Claude Desktop

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Woodpecker CI and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Woodpecker CI to Claude Desktop 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Woodpecker CI in Claude Desktop

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 Desktop 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.

Woodpecker CI
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Woodpecker CI for Claude Desktop

Every tool call from Claude Desktop to the Woodpecker CI MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Explore More MCP Servers

View all →