Woodpecker CI Connector for AI agents.

34 live capabilities

Manage CI/CD pipelines and build agents using natural language.

Live agent request Woodpecker CI / Connector

Waiting for input…

AI Agent

Why people use Woodpecker CI

Fix Broken Builds Faster with Woodpecker CI

This Connector changes that by bringing the CI/CD dashboard into your chat interface. You can just tell your agent to restart a build or check why a specific task is pending. It turns a multi-click process into a single sentence, letting you stay in your flow.

What Vinkius changes

You get a natural language interface for your entire CI/CD infrastructure.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

Real-world use case 01

Restarting a failed build

A developer sees a failed build in their terminal.
Real-world use case 02

Checking agent capacity

An SRE notices slow build times.
Real-world use case 03

Fixing webhook issues

A project stops building on push.

Complete set · 34capabilities

The complete Woodpecker CI capability set.

These are the exact actions your AI can choose when you ask it to work with Woodpecker CI.

Capability set01 / 09

01—04

4 capabilities in this set.

Part of 34 available through Woodpecker CI.

01 Capability
Get pipeline config
Get the configuration files used for a pipeline. This is great for debugging build steps.
02 Capability
List org secrets
List organization-level secrets. Use this to manage shared credentials for a group of projects.
03 Capability
List orgs
List all organizations. This helps you see the scope of your CI/CD environment.
04 Capability
Create agent
Create a new Woodpecker agent. This helps you scale your build capacity across different machines.

Capability set02 / 09

05—08

4 capabilities in this set.

Part of 34 available through Woodpecker CI.

05 Capability
Delete agent
Delete an agent. Use this to clean up old runners or decommission hardware.
06 Capability
Get org permissions
Get user permissions for an organization. Use this for auditing and access control.
07 Capability
Get repo
Get repository details. This helps you confirm the slug and status of a project.
08 Capability
List agents
List all Woodpecker agents. This helps you monitor your total build capacity.

Capability set03 / 09

09—12

4 capabilities in this set.

Part of 34 available through Woodpecker CI.

09 Capability
Cancel pipeline
Cancel a running pipeline. Use this to stop a build that is stuck or no longer needed.
10 Capability
Chown repo
Change repository owner to the current user. Use this to quickly reassign project permissions.
11 Capability
Create global secret
Create a global secret. This is ideal for shared credentials like internal API keys.
12 Capability
Create repo secret
Create a repository secret. Use this to store environment variables like database passwords.

Capability set04 / 09

13—16

4 capabilities in this set.

Part of 34 available through Woodpecker CI.

13 Capability
Delete pipeline
Delete a pipeline. This helps keep your project history clean.
14 Capability
Delete repo
Deactivate or delete a repository. Use this when you no longer need a project's CI configuration.
15 Capability
Get agent
Get details of a specific agent. This helps you check its configuration and current status.
16 Capability
Get healthz
Server health check. Use this to see if your instance is responding correctly.

Capability set05 / 09

17—20

4 capabilities in this set.

Part of 34 available through Woodpecker CI.

17 Capability
Get metrics
Prometheus metrics. This provides data on performance and resource usage for your infrastructure.
18 Capability
Get pipeline
Get details of a specific pipeline. Use this to see the status and ID of a recent build.
19 Capability
Get user
Get the currently authenticated user. Use this to confirm your identity within the system.
20 Capability
Get version
Get server version information. This is helpful for verifying you are on the latest release.

Capability set06 / 09

21—24

4 capabilities in this set.

Part of 34 available through Woodpecker CI.

21 Capability
List agent tasks
List tasks currently assigned to an agent. Use this to troubleshoot why a build is pending.
22 Capability
List global secrets
List global secrets. Only use this if you have the necessary admin permissions.
23 Capability
List org agents
List agents scoped to an organization. This is useful for managing multi-tenant setups.
24 Capability
List pipelines
List pipelines for a repository. Use this to track the history of your builds.

Capability set07 / 09

25—28

4 capabilities in this set.

Part of 34 available through Woodpecker CI.

25 Capability
List repo secrets
List repository-level secrets. Use this to audit the credentials available to a project.
26 Capability
List repos
List all repositories on the server. This helps you see every project you are tracking.
27 Capability
List users
List all users. Only use this if you have admin rights for the system.
28 Capability
Lookup repo
Lookup a repository by its full name. Use this to quickly locate a project in a large organization.

Capability set08 / 09

29—31

3 capabilities in this set.

Part of 34 available through Woodpecker CI.

29 Capability
Repair repo
Repair repository webhooks. Use this when a project stops triggering builds automatically.
30 Capability
Restart pipeline
Restart a pipeline. This is the quickest way to re-run a failed build.
31 Capability
Trigger pipeline
Trigger a manual pipeline. Use this to kick off a build on demand without a new commit.

Capability set09 / 09

32—34

3 capabilities in this set.

Part of 34 available through Woodpecker CI.

32 Capability
Update agent
Update an existing agent. Use this to update runner settings or environment variables.
33 Capability
Update repo
Update repository settings. Use this to modify project names or visibility.
34 Capability
Activate repo
Activate a repository. Use this to make a new project available for CI/CD.

Set up in minutes

One URL. Then ask Woodpecker CI to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Woodpecker CI from the conversation.

Choose your client

Live preview

Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_FerYBzPY1px1PeVxdzIkY0bEgd6qWRE3xebiZbq6/mcp

Step 01

Open Connectors

In Claude Web or Claude Desktop, open Settings and choose Connectors.
Step 02

Add the URL

Choose Add custom connector, name it Woodpecker CI, and paste the URL above.
Step 03

Turn it on in chat

Select +, open Connectors, and enable Woodpecker CI for the conversation.

ChatGPT · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_FerYBzPY1px1PeVxdzIkY0bEgd6qWRE3xebiZbq6/mcp

Step 01

Open MCP settings

On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
Step 02

Add the URL

Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Woodpecker CI URL.
Step 03

Save and start

Save the connection and enable Woodpecker CI in your conversation. Desktop may ask you to restart once.

Cursor · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "woodpecker-ci": {
      "url": "https://edge.vinkius.com/vk_preview_FerYBzPY1px1PeVxdzIkY0bEgd6qWRE3xebiZbq6/mcp"
    }
  }
}

Step 01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Step 02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
Step 03

Save the file

Cursor will automatically detect the new Connector
Step 04

Start using Woodpecker CI

Open Agent mode in chat and ask: "Using Woodpecker CI, help me...". 34 tools available

VS Code Copilot · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "woodpecker-ci": {
      "url": "https://edge.vinkius.com/vk_preview_FerYBzPY1px1PeVxdzIkY0bEgd6qWRE3xebiZbq6/mcp"
    }
  }
}

Step 01

Create MCP config

Create a .vscode/mcp.json file in your project root
Step 02

Add the server config

Paste the JSON configuration above
Step 03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Step 04

Start using Woodpecker CI

Ask Copilot: "Using Woodpecker CI, help me...". 34 tools available

Windsurf · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "woodpecker-ci": {
      "url": "https://edge.vinkius.com/vk_preview_FerYBzPY1px1PeVxdzIkY0bEgd6qWRE3xebiZbq6/mcp"
    }
  }
}

Step 01

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
Step 02

Add the server

Paste the JSON configuration above into mcp_config.json
Step 03

Save and reload

Windsurf will detect the new server automatically
Step 04

Start using Woodpecker CI

Open Cascade and ask: "Using Woodpecker CI, help me...". 34 tools available

Cline · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "woodpecker-ci": {
      "url": "https://edge.vinkius.com/vk_preview_FerYBzPY1px1PeVxdzIkY0bEgd6qWRE3xebiZbq6/mcp"
    }
  }
}

Step 01

Open Cline MCP Settings

Click the Connectors icon in the Cline sidebar panel
Step 02

Add remote server

Click "Add Connector" and paste the configuration above
Step 03

Enable the server

Toggle the server switch to ON
Step 04

Start using Woodpecker CI

Ask Cline: "Using Woodpecker CI, help me...". 34 tools available

Claude Code · Terminal command

Official guide ↗

Advanced setup

claude mcp add woodpecker-ci --transport http "https://edge.vinkius.com/vk_preview_FerYBzPY1px1PeVxdzIkY0bEgd6qWRE3xebiZbq6/mcp"

Step 01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed
Step 02

Add the Connector

Run the command above in your terminal
Step 03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session
Step 04

Start using Woodpecker CI

Ask Claude: "Using Woodpecker CI, show me...". 34 tools are ready

Where the request belongs

Work Woodpecker CI can move forward.

Built around the request

This is for the DevOps engineer who is tired of context switching between their code editor and the CI dashboard. It is for the developer who just wants to kick off a build without hunting for a button.

01

DevOps Engineer

You use this to monitor build agent health and troubleshoot failing pipelines across multiple repositories.

02

Software Developer

You use this to quickly trigger manual builds or check the status of your latest deployment from your editor.

03

SRE

You use this to audit organization permissions and manage global secrets across the infrastructure.

Build the capability set

Each Connector adds new actions and data without changing how you work.

Browse Connectors

01 36 capabilities

Semaphore

Automate CI/CD workflows, manage pipelines, and monitor build jobs directly from your AI agent.

02 10 capabilities

Travis CI

Manage CI/CD pipelines, trigger custom builds, and oversee repository testing health securely via your AI agent.

03 39 capabilities

Drone CI

Automate your CI/CD workflows with Drone CI—manage repositories, monitor builds, and handle secrets directly from your AI agent.

04 11 capabilities

Buildkite

Automate CI/CD pipelines via Buildkite. manage builds, agents, and deployments directly from any AI agent.

05 8 capabilities

Codefresh

Manage CI/CD and GitOps via Codefresh. track pipelines, trigger builds, and monitor delivery clusters directly from any AI agent.

06 11 capabilities

Harness

Automate CI/CD and DevOps workflows via Harness. manage pipelines, executions, and secrets directly from any AI agent.

Bring your own AI

Change the model, client or framework. Keep Woodpecker CI connected.

Before you connect

Questions about Woodpecker CI.

The practical details behind the request, access and result.

How do I use Woodpecker CI MCP to manage my builds?

You can use your AI agent to trigger builds, restart failed pipelines, and check the status of any repository. It replaces the need to manually click through the Woodpecker dashboard.

Can I use Woodpecker CI MCP to fix broken webhooks?

Yes. If your repository stops triggering builds automatically, you can ask the agent to repair the webhooks for that specific project.

Is Woodpecker CI MCP good for managing secrets?

It's a great way to manage credentials. You can create global or repository-specific secrets and list them using natural language commands.

How do I check my agent status with Woodpecker CI MCP?

You can simply ask your agent to list your runners or check their health. It will show you which ones are online and how many tasks they are currently running.

Can Woodpecker CI MCP trigger a build manually?

Yes, you can tell your agent to trigger a manual pipeline for any repository. This is perfect for testing changes without needing to commit new code.

Can I use Woodpecker CI MCP to see my pipeline history?

You can ask the agent to list the pipelines for a specific repository. It will show you the history of recent builds, including their success or failure status.

Can I trigger a new pipeline build for a specific repository?

Yes. Use the trigger_pipeline capability 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 capabilities like create_repo_secret and list_repo_secrets to manage sensitive variables at the repository level, as well as global and organization-level secret capabilities.

One connection away

Give your agent a direct line to Woodpecker CI.

Connect Woodpecker CI once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available