Woodpecker CI MCP server

What the model can do

Woodpecker CI (self-hosted): the repositories it builds with their last pipeline, the recent pipeline feed, a repository's pipelines filtered by branch, event and status, and one pipeline's workflows and steps. Can trigger, restart, approve, decline, cancel or delete a pipeline, and list, create, run or delete cron jobs when asked.

Reads

• woodpecker_list_reposRepositories the token's user can see in Woodpecker, with each one's last pipeline (number, status, branch, when).
• woodpecker_feedThe latest pipeline of each repository the token's user follows, newest first: status, branch, event, author and times.
• woodpecker_list_pipelinesPipelines of one Woodpecker repository, newest first, filtered by branch, event (push, pull_request, tag, deployment, cron, manual)…
• woodpecker_get_pipelineOne Woodpecker pipeline with its workflows and steps: each step's state, exit code and error.
• woodpecker_list_cronsCron jobs of one Woodpecker repository: id, name, schedule, branch, whether enabled and when it next runs.

Acts, when you ask

These change something in Woodpecker CI. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• woodpecker_trigger_pipelineStarts compute, run a repository's pipeline manually on a branch in Woodpecker.
• woodpecker_restart_pipelineStarts compute, restart a finished Woodpecker pipeline.
• woodpecker_cancel_pipelineStops work, cancel a pending or running Woodpecker pipeline.
• woodpecker_delete_pipelineDeletes permanently, delete a finished Woodpecker pipeline together with its steps and their logs.
• woodpecker_approve_pipelineStarts compute, approve a Woodpecker pipeline that is waiting for approval (typically from a fork or an untrusted author), which starts it.
• woodpecker_decline_pipelineDecline a Woodpecker pipeline that is waiting for approval, so it does not run.
• woodpecker_create_cronCreate a Woodpecker cron job that runs a branch's pipeline on a schedule from now on, each run using agent time and doing whatever the pipeline does…
• woodpecker_run_cronStarts compute, run a Woodpecker cron job's pipeline now, outside its schedule.
• woodpecker_delete_cronDeletes, remove a Woodpecker cron job so its scheduled runs stop.

Connect it

First connect Woodpecker CI on Dashboard → Connections, then add Memtro to your client once. The Woodpecker CI tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Woodpecker CI connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Is the main branch of the web repository green?
• › What is red in CI right now?
• › Which step failed in the last pull request pipeline?
• › How many cron pipelines failed this week?
• › Restart the last pipeline on the Acme api repository

Questions

Is this an official Woodpecker CI MCP server?

No. It is Memtro's MCP server with Memtro's Woodpecker CI connector behind it: the connector reads Woodpecker CI through its API with the credentials you connect on Dashboard → Connections, and Woodpecker CI publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Woodpecker CI?

Only when you ask, and only what it has been granted: trigger a pipeline on a branch (it runs the repository's pipeline, which may deploy or publish); restart a finished pipeline (runs it again); cancel a pending or running pipeline; delete a finished pipeline and its logs permanently; approve a pipeline waiting for approval, which starts it; decline a pipeline waiting for approval; create a cron job that runs a branch's pipeline on a schedule; run a cron job's pipeline now; delete a cron job. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server