Woodpecker CI MCP Server for Claude DesktopGive Claude Desktop instant access to 34 tools to Activate Repo, Cancel Pipeline, Chown Repo, and more

Name: Woodpecker CI
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

Open in ChatGPT Open in Claude Open in Perplexity

The Woodpecker CI MCP Server for Claude Desktop is a standout in the Ship It category — giving your AI agent 34 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

{
  "mcpServers": {
    "woodpecker-ci": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Woodpecker CI and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

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

About Woodpecker CI MCP Server

Connect your Woodpecker CI server to any AI agent to automate your continuous integration and deployment workflows through natural language.

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.

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.

The Woodpecker CI MCP Server exposes 34 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 34 Woodpecker CI tools available for Claude Desktop

When Claude Desktop connects to Woodpecker CI through Vinkius, your AI agent gets direct access to every tool listed below — spanning ci-cd, pipelines, automation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

activate

Activate repo on Woodpecker CI

Activate a repository

cancel

Cancel pipeline on Woodpecker CI

Cancel a running pipeline

chown

Chown repo on Woodpecker CI

Change repository owner to the current user

create

Create agent on Woodpecker CI

Create a new Woodpecker agent

create

Create global secret on Woodpecker CI

Create a global secret

create

Create repo secret on Woodpecker CI

Create a repository secret

delete

Delete agent on Woodpecker CI

Delete an agent

delete

Delete pipeline on Woodpecker CI

Delete a pipeline

delete

Delete repo on Woodpecker CI

Deactivate/delete a repository

get

Get agent on Woodpecker CI

Get details of a specific agent

get

Get healthz on Woodpecker CI

Server health check

get

Get metrics on Woodpecker CI

Prometheus metrics (requires WOODPECKER_PROMETHEUS_AUTH_TOKEN if configured)

get

Get org permissions on Woodpecker CI

Get user permissions for an organization

get

Get pipeline on Woodpecker CI

Get details of a specific pipeline

get

Get pipeline config on Woodpecker CI

Get the configuration files used for a pipeline

get

Get repo on Woodpecker CI

Get repository details

get

Get user on Woodpecker CI

Get the currently authenticated user

get

Get version on Woodpecker CI

Get server version information

list

List agent tasks on Woodpecker CI

List tasks currently assigned to an agent

list

List agents on Woodpecker CI

List all Woodpecker agents

list

List global secrets on Woodpecker CI

List global secrets (Admin only)

list

List org agents on Woodpecker CI

List agents scoped to an organization

list

List org secrets on Woodpecker CI

List organization-level secrets

list

List orgs on Woodpecker CI

List all organizations

list

List pipelines on Woodpecker CI

List pipelines for a repository

list

List repo secrets on Woodpecker CI

List repository-level secrets

list

List repos on Woodpecker CI

List all repositories on the server

list

List users on Woodpecker CI

List all users (Admin only)

lookup

Lookup repo on Woodpecker CI

Lookup a repository by its full name (slug)

repair

Repair repo on Woodpecker CI

Repair repository webhooks

restart

Restart pipeline on Woodpecker CI

Restart a pipeline

trigger

Trigger pipeline on Woodpecker CI

Trigger a manual pipeline

update

Update agent on Woodpecker CI

Update an existing agent

update

Update repo on Woodpecker CI

Update repository settings

Connect Woodpecker CI to Claude Desktop via MCP

Follow these steps to wire Woodpecker CI into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Woodpecker CI

Look for the 🔌 icon in the chat. your 34 tools are now available

Why Use Claude Desktop with the Woodpecker CI MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Woodpecker CI through the Model Context Protocol.

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

Woodpecker CI + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Woodpecker CI MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for Woodpecker CI in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Woodpecker CI immediately.

"List all Woodpecker agents and show their current status."

"Find the repository 'vinkius/mcp-server' and trigger a new pipeline."

"Show me the last 5 pipelines for repository ID 42."

Troubleshooting Woodpecker CI MCP Server with Claude Desktop

Common issues when connecting Woodpecker CI to Claude Desktop through Vinkius, and how to resolve them.

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

Authentication error

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

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.

Woodpecker CI + Claude Desktop FAQ

Common questions about integrating Woodpecker CI MCP Server with Claude Desktop.

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.

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.

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.

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.

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.