Woodpecker CI MCP server

Read from the package source without running it. The installed server may list more.

• activate_repository

  Turns on Woodpecker for a repository that exists in the forge, which

• approve_pipeline

  Releases a pipeline that is waiting for approval (status "blocked") and

• cancel_pipelinewrite action

  Stops a pipeline that is pending or running. Its steps are killed where

• chown_repository

  Makes the authenticated account the repository's owner in Woodpecker. The

• create_agentwrite action

  Registers a new build agent and returns its token. THE TOKEN IS A

• create_cronwrite action

  Schedules a pipeline run. The pipeline runs with event "cron", so steps

• create_forgewrite action

  Registers an additional forge. Admin only, and two-step: a forge is a

• create_registrywrite action

  Stores credentials for a container registry so pipelines can pull private

• create_secretwrite action

  Creates a secret at the chosen level. The value is write-only: it is never

• create_userwrite action

  Registers an account ahead of its first login. Admin only. This does not

• decline_pipeline

  Refuses a pipeline that is waiting for approval. It ends as "declined" and

• delete_agentwrite action

  Removes an agent and invalidates its token. Anything it was running is

• delete_cronwrite action

  Removes a scheduled run. If you only want it to stop for now,

• delete_forgewrite action

  Removes a forge from Woodpecker. Admin only. Everyone who signs in through

• delete_organizationwrite action

  Removes an organization from Woodpecker together with its org-level

• delete_pipelinewrite action

  Removes a pipeline and everything attached to it, including its logs.

• delete_pipeline_logswrite action

  Deletes the stored output of every step of a pipeline. The pipeline and its

• delete_registrywrite action

  Removes stored credentials for a registry. Pipelines that pull private

• delete_repositorywrite action

  Removes a repository from Woodpecker: the webhook, every pipeline, all

• delete_secretwrite action

  Deletes a secret. Any pipeline that reads it starts failing — or worse,

• delete_step_logswrite action

  Deletes the stored output of a single step. The step and the pipeline stay,

• delete_userwrite action

  Removes an account from Woodpecker. Admin only. Repositories the account

• get_agent

  Returns one agent. Admin only. Its token is redacted; an agent that lost

• get_cron

  Returns one cron job, including the variables it passes.

• get_current_user

  Returns the account WOODPECKER_TOKEN belongs to, including whether it is

• get_forge

  Returns one forge configuration. Admin only. The OAuth client secret is

• get_log_level

  Returns the current log level of the Woodpecker server. Admin only.

• get_organization

  Returns one organization by its numeric id.

• get_organization_permissions

  What the authenticated account may do in this organization: member and

• get_pipeline

  Returns one pipeline with its workflows and steps, including each step id

• get_pipeline_config

  Returns the pipeline YAML files this run was built from, as they were at

• get_pipeline_feed

  The activity feed of the authenticated account: the latest pipeline of

• get_pipeline_metadata

  Returns the metadata Woodpecker exposes to the pipeline itself — the

• get_queue_info

  The server-side build queue: what is pending, running and waiting on an

• get_registry

  Returns one registry entry — its address and username. The password is

• get_repository

  Returns the full Woodpecker configuration of one repository: trusted

• get_repository_permissions

  What the authenticated account may do with this repository: pull, push

• get_secret

  Returns one secret's metadata: which events and images it applies to, and

• get_server_info

  Returns the Woodpecker version and whether the server reports itself

• get_step_logs

  Returns the output of one pipeline step as text, newest end first by

• get_user

  Returns one account by its login. Admin only. forge_id is required — see

• list_agent_tasks

  The work an agent is currently running. Admin only. This is how you find

• list_agents

  Lists the build agents, with their platform, capacity, version and last

• list_crons

  Lists the scheduled pipeline runs of a repository, with the next execution

• list_forges

  Lists the forges this Woodpecker authenticates against. Admin only. The

• list_organizations

  Lists the organizations known to this Woodpecker instance. Admin only.

• list_pipelines

  Lists a repository's pipelines, newest first, summarised to what a list

• list_pull_requests

  Lists the open pull requests of a repository, with the index a pipeline

• list_queued_pipelines

  Lists the pipelines waiting in the server queue across all repositories.

• list_registries

  Lists the container registry credentials at one level. These are what let

• list_repositories

  Lists repositories. By default the ones the authenticated account can

• list_repository_branches

  Lists the branches of a repository, as Woodpecker sees them in the forge.

• list_secrets

  Lists the secrets at one level — repository, organization or instance-wide.

• list_users

  Lists the accounts known to this Woodpecker instance. Admin only.

• lookup_organization

  Resolves an organization name to its id — the id every other org-level

• lookup_repository

  Resolves an "owner/name" pair to a repository id. Every other repository

• move_repository

  Tells Woodpecker that a repository moved to a different owner or name in

• pause_queue

  Stops the server from handing new work to agents. Running pipelines finish;

• repair_repository

  Re-installs the forge webhook and refreshes the stored repository data.

• restart_pipelinewrite action

  Runs an existing pipeline again, at the same commit and with the same

• resume_queue

  Lets the server hand work to agents again. Admin only. Queued pipelines

• run_cronwrite action

  Starts the cron job's pipeline immediately, without waiting for its

• set_log_level

  Changes the log level of the running Woodpecker server, without a restart.

• trigger_pipeline

  Starts a pipeline manually on a branch. It runs the config as it is in

• update_agentwrite action

  Changes an agent. Admin only. no_schedule=true is the drain switch: the

• update_cronwrite action

  Changes a cron job. Only the fields you pass are touched — including

• update_forgewrite action

  Changes a forge configuration. Admin only, and two-step: this is the

• update_registrywrite action

  Changes the username or password of a registry entry. The address itself

• update_repositorywrite action

  Changes Woodpecker settings of a repository. Only the fields you pass are

• update_secretwrite action

  Changes a secret. Only the fields you pass are touched — but "events" and

• update_userwrite action

  Changes an account. Admin only. The one that matters is "admin": granting

• Code scan55 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

83/100

higher than 65% of 1,119 Developer tools servers

Tools

71

the typical Developer tools server has 7

Tools that change things

38%

typical: 5%. Fewer write tools means less an agent can break

Downloads a week

45

more than 33% of 436 Developer tools servers with a package

Woodpecker CI: common questions

Is Woodpecker CI MCP server safe?

Mostly: it is graded B (83/100). Read the Woodpecker CI safety report

How do I install Woodpecker CI?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Woodpecker CI need an API key?

Yes. The registry entry asks for WOODPECKER_TOKEN.

Is Woodpecker CI maintained?

The last commit was 20 days ago (2026-10-15). The latest release is v0.4.0.

What can I use instead of Woodpecker CI?

Servers from other publishers that do the same job: GitLab MCP Server, GitDiagram MCP server and walkerOS Flow MCP server.

How does Woodpecker CI compare with other Developer tools MCP servers?

safety score 83/100 (higher than 65% of 1,119 Developer tools servers); tools 71 (the typical Developer tools server has 7); tools that change things 38% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.