convez.ai
MCP ServerDevOps & InfraestruturaIntermediário
coredeskdev

Woodpecker CI MCP Server

coredeskdev/woodpecker-ci-mcp-server

Integre Woodpecker CI com Claude e assistentes IA para inspecionar pipelines

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que integra Woodpecker CI com assistentes de IA como Claude, permitindo ler pipelines, workflows, steps e logs de build decodificados. Zero dependências, arquivo único e baseado em stdio para inspeção e debug de falhas em CI/CD.

Instalação

$npx convez-ai coredeskdev/woodpecker-ci-mcp-server

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
1
Acompanhando
0
Saúde
50%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Debugar falhas de pipeline via chat
  • Inspecionar logs de build com IA
  • Analisar histórico de pipelines e workflows
  • Automação e análise de CI/CD

Veredito

Ferramenta técnica bem executada para times DevOps que usam Woodpecker e querem conversar com IA sobre pipelines. Zero dependências e simples, mas requer configuração manual de token e URL. Ótima ponte entre Woodpecker e ecossistema Claude.

README

A tradução para o português deste README ainda está na fila.

Woodpecker CI MCP Server

A Model Context Protocol (MCP) server for Woodpecker CI — let AI assistants like Claude, Claude Code, Cursor, and any MCP-compatible client read your CI pipelines, inspect workflows and steps, and pull decoded build logs to debug failures.

MCP Node License: MIT Dependencies: 0

Keywords: Woodpecker CI, MCP server, Model Context Protocol, CI/CD, pipeline logs, build logs, Claude, Claude Code, Anthropic, AI DevOps assistant, LLM tools, continuous integration.


What it does

This is a tiny, single-file, zero-dependency MCP server that wraps the Woodpecker CI REST API. Once connected, your AI assistant can answer questions like:

  • "Why did the latest pipeline on main fail?"
  • "Show me the logs for the failed lint step in pipeline #2105."
  • "List the last 20 pipelines for repo 1 and tell me which ones are red."

It speaks MCP over stdio, uses only the built-in fetch from Node 18+, and reads its configuration from two environment variables. Nothing is hardcoded.

Tools

ToolParametersReturns
woodpecker_list_repos–Repositories the token can access (id, full name, default branch)
woodpecker_list_pipelinesrepo_id, limit? (default 20)Recent pipelines with status, event, branch, commit, message
woodpecker_get_pipelinerepo_id, numberPipeline status + full workflow/step tree (with step ids for logs)
woodpecker_pipeline_logsrepo_id, number, step_id, tail?Decoded logs for a single step (base64 from the API is decoded for you)

Read-only by design — the server only performs GET requests. It never starts, stops, approves, or deletes pipelines.

Requirements

  • Node.js ≥ 18 (uses the built-in global fetch)
  • A Woodpecker Personal Access Token (see below)

Configuration

The server is configured entirely through environment variables — there are no default URLs or tokens baked into the code:

VariableRequiredDescription
WOODPECKER_URLyesBase URL of your Woodpecker instance, e.g. https://your-woodpecker.example.com (no trailing slash)
WOODPECKER_TOKENyesYour Woodpecker Personal Access Token (JWT)

Get a Personal Access Token

In the Woodpecker UI: User settings → CLI and API → Personal Access Token. Copy the token.

Find your repo_id

It is the numeric id in the repo URL (/repos/<id>/...) or via woodpecker_list_repos.

Installation

Clone the repo (or copy server.mjs anywhere — it has no dependencies to install):

git clone https://github.com/coredeskdev/woodpecker-ci-mcp-server.git

Claude Code (CLI)

claude mcp add woodpecker \
  -s user \
  -e WOODPECKER_URL=https://your-woodpecker.example.com \
  -e WOODPECKER_TOKEN=your-token \
  -- node /absolute/path/to/woodpecker-ci-mcp-server/server.mjs

-s user makes it available across all your projects on this machine. Drop it for the current project only.

Claude Desktop / generic MCP client

Add to your MCP config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "woodpecker": {
      "command": "node",
      "args": ["/absolute/path/to/woodpecker-ci-mcp-server/server.mjs"],
      "env": {
        "WOODPECKER_URL": "https://your-woodpecker.example.com",
        "WOODPECKER_TOKEN": "your-token"
      }
    }
  }
}

Cursor / Windsurf / other MCP hosts

Any host that supports stdio MCP servers works — point the command at node and the args at server.mjs, and pass the two env vars.

Example prompts

Once connected, try:

  • "Using the woodpecker tools, list the last 10 pipelines for repo 1."
  • "Get pipeline 2105 in repo 1 and tell me which step failed and why."
  • "Show me the last 40 lines of the logs for step 38613 in pipeline 2105, repo 1."

How it works

The server implements the MCP JSON-RPC 2.0 handshake (initialize, tools/list, tools/call) over stdio. Each tool issues an authenticated GET to ${WOODPECKER_URL}/api/... with Authorization: Bearer ${WOODPECKER_TOKEN}. Step logs come back base64-encoded per line from the Woodpecker API; the server decodes and concatenates them for you. Diagnostic output goes to stderr so it never corrupts the stdout JSON-RPC stream.

Security

  • Treat WOODPECKER_TOKEN like a password. Prefer your MCP client's env/secret storage over committing it anywhere.
  • .env is git-ignored; only .env.example (with placeholders) is tracked.
  • The server is read-only (GET-only), reducing blast radius if a token leaks.

Manual smoke test

WOODPECKER_URL=https://your-woodpecker.example.com \
WOODPECKER_TOKEN=your-token \
node server.mjs
# then paste an MCP initialize frame on stdin, or just rely on your MCP client.

License

MIT © coredeskdev


This project is an independent, community-built integration and is not affiliated with or endorsed by the Woodpecker CI project or Anthropic.

Ver o original no GitHub

Bom para

Relacionados