Woodpecker CI

Woodpecker CI MCP Connector for Claude

A+

Manage your Woodpecker CI instance — control pipelines, monitor agents, and configure repositories directly from your AI agent.

34 tools Official Updated Jun 28, 2026 Official Vinkius Partner

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.
ci-cdpipelinesautomationdeploymentmonitoringbuild-management

34 tools expose this connector's capabilities to your AI agent.

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_config

Get the configuration files used for a pipeline

get_pipeline

Get details of a specific 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

See how to talk to your AI agent using Woodpecker CI.

List all Woodpecker agents and show their current status.

I've retrieved the agent list. You have 3 agents: 'docker-runner-01' (Online), 'k8s-agent-alpha' (Online), and 'legacy-local' (Offline). Would you like to see the tasks assigned to 'docker-runner-01'?

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

Found it (ID: 42). I have triggered a new pipeline for 'vinkius/mcp-server'. The new pipeline is #154. You can monitor its progress or I can notify you when it finishes.

Show me the last 5 pipelines for repository ID 42.

Here are the 5 most recent pipelines for repo 42: #153 (Success), #152 (Failure), #151 (Success), #150 (Success), and #149 (Cancelled). Pipeline #152 failed at the 'test' step. Would you like to see the config for that build?

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.

Related Connectors