Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Woodpecker CI

by ni-cversion 0.4.0i★ 1iRuns on your computerOfficial site ↗
Registry nameio.github.ni-c/woodpecker-ci-mcp

How to install

What it does

Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons

  • Connects Runs on your computer
  • Account or key Needs WOODPECKER_TOKEN · 1 setting to fill in (WOODPECKER_URL)
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 468,7331 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,3321 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 150,2871 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity4/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score16/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Woodpecker CI. Follow https://mcp.popnx.com/i/ni-c-woodpecker-ci-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Woodpecker CI for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "woodpecker-ci": { "command": "npx", "args": [ "-y", "@ni-c/woodpecker-ci-mcp" ], "env": { "WOODPECKER_URL": "your-value", "WOODPECKER_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For WOODPECKER_TOKEN, WOODPECKER_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Woodpecker CI tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Woodpecker CI key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Woodpecker CI site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WOODPECKER_URL Root URL of the Woodpecker server, e.g. https://woodpecker.example.com

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "woodpecker-ci": {
          "command": "npx",
          "args": [
            "-y",
            "@ni-c/woodpecker-ci-mcp"
          ],
          "env": {
            "WOODPECKER_URL": "your-value",
            "WOODPECKER_TOKEN": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Woodpecker CI and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Woodpecker CI or shows a Woodpecker CI tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WOODPECKER_READ_ONLY Set to true to register only the read tools (default: false)
  • WOODPECKER_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
  • WOODPECKER_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
  • WOODPECKER_INSECURE_TLS Set to true to accept a self-signed certificate from the Woodpecker server (default: false)
  • WOODPECKER_API_PREFIX Path of the API below the server root (default: /api; Crow CI 5 and later: /api/v1)

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Woodpecker CI yet

Woodpecker CI runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Woodpecker CI

  • You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time)
  • You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time)
  • You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Woodpecker CI for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user woodpecker-ci --env WOODPECKER_URL=your-value --env WOODPECKER_TOKEN=your-value -- npx -y @ni-c/woodpecker-ci-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For WOODPECKER_TOKEN, WOODPECKER_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Woodpecker CI tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Woodpecker CI key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Woodpecker CI site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WOODPECKER_URL Root URL of the Woodpecker server, e.g. https://woodpecker.example.com

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    claude mcp add --scope user woodpecker-ci --env WOODPECKER_URL=your-value --env WOODPECKER_TOKEN=your-value -- npx -y @ni-c/woodpecker-ci-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Woodpecker CI listed as connected

  7. Try it

    Use Woodpecker CI and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Woodpecker CI or shows a Woodpecker CI tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WOODPECKER_READ_ONLY Set to true to register only the read tools (default: false)
  • WOODPECKER_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
  • WOODPECKER_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
  • WOODPECKER_INSECURE_TLS Set to true to accept a self-signed certificate from the Woodpecker server (default: false)
  • WOODPECKER_API_PREFIX Path of the API below the server root (default: /api; Crow CI 5 and later: /api/v1)

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Woodpecker CI for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "woodpecker-ci": { "command": "npx", "args": [ "-y", "@ni-c/woodpecker-ci-mcp" ], "env": { "WOODPECKER_URL": "your-value", "WOODPECKER_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For WOODPECKER_TOKEN, WOODPECKER_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Woodpecker CI tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Woodpecker CI key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Woodpecker CI site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WOODPECKER_URL Root URL of the Woodpecker server, e.g. https://woodpecker.example.com

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Woodpecker CI settings, WOODPECKER_TOKEN, WOODPECKER_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Woodpecker CI and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Woodpecker CI or shows a Woodpecker CI tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WOODPECKER_READ_ONLY Set to true to register only the read tools (default: false)
  • WOODPECKER_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
  • WOODPECKER_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
  • WOODPECKER_INSECURE_TLS Set to true to accept a self-signed certificate from the Woodpecker server (default: false)
  • WOODPECKER_API_PREFIX Path of the API below the server root (default: /api; Crow CI 5 and later: /api/v1)

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Woodpecker CI key (create it on the maker’s site) · 1 setting(s) to fill in (WOODPECKER_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Woodpecker CI for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "woodpecker-ci": { "type": "stdio", "command": "npx", "args": [ "-y", "@ni-c/woodpecker-ci-mcp" ], "env": { "WOODPECKER_URL": "your-value", "WOODPECKER_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For WOODPECKER_TOKEN, WOODPECKER_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Woodpecker CI tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Woodpecker CI key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Woodpecker CI site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • WOODPECKER_URL Root URL of the Woodpecker server, e.g. https://woodpecker.example.com

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Woodpecker CI settings, WOODPECKER_TOKEN, WOODPECKER_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Woodpecker CI and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Woodpecker CI or shows a Woodpecker CI tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • WOODPECKER_READ_ONLY Set to true to register only the read tools (default: false)
  • WOODPECKER_ALLOW_TOOLS Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
  • WOODPECKER_DENY_TOOLS Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
  • WOODPECKER_INSECURE_TLS Set to true to accept a self-signed certificate from the Woodpecker server (default: false)
  • WOODPECKER_API_PREFIX Path of the API below the server root (default: /api; Crow CI 5 and later: /api/v1)

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Woodpecker CI💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user woodpecker-ci --env WOODPECKER_URL=your-value --env WOODPECKER_TOKEN=your-value -- npx -y @ni-c/woodpecker-ci-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "woodpecker-ci": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_URL": "your-value",
        "WOODPECKER_TOKEN": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "woodpecker-ci": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_URL": "your-value",
        "WOODPECKER_TOKEN": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "woodpecker-ci": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ],
      "env": {
        "WOODPECKER_URL": "your-value",
        "WOODPECKER_TOKEN": "your-value"
      }
    }
  }
}

Values you fill in

  • WOODPECKER_URL required env
    Root URL of the Woodpecker server, e.g. https://woodpecker.example.com
  • WOODPECKER_TOKEN secret required env
    Personal access token from the Woodpecker user settings
  • WOODPECKER_READ_ONLY env
    Set to true to register only the read tools (default: false)
  • WOODPECKER_ALLOW_TOOLS env
    Comma-separated tool names or list_* prefixes to register; 'essential' selects a curated preset (default: all tools)
  • WOODPECKER_DENY_TOOLS env
    Comma-separated tool names or list_* prefixes to remove from whatever the allow list left
  • WOODPECKER_INSECURE_TLS env
    Set to true to accept a self-signed certificate from the Woodpecker server (default: false)
  • WOODPECKER_API_PREFIX env
    Path of the API below the server root (default: /api; Crow CI 5 and later: /api/v1)

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
60/wk
Connection
Runs on your computer
Latest versioni
0.4.0
Published to registryi
Oct 15, 2026
Code last changedi
Nov 12, 2026
Maker
ni-c
Packages
npm: @ni-c/woodpecker-ci-mcp
oci: ghcr.io/ni-c/woodpecker-ci-mcp:0.4.0
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ni-c, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 8 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @ni-c/woodpecker-ci-mcp@0.4.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/ni-c-woodpecker-ci-mcp.svg)](https://mcp.popnx.com/en/servers/ni-c-woodpecker-ci-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 69% of the other 6202 servers in this category
  • Published to the registry more recently than 47% of the other 6202 servers in this category
  • Basic checks equal to or better than 99% of the other 6202 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Woodpecker CI safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: WOODPECKER_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 8 days ago, and the latest version (0.4.0) reached the registry 36 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 7 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
Woodpecker CI
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

woodpecker-ci-mcp

A Model Context Protocol (MCP) server for Woodpecker CI, the lightweight container-native CI engine — it runs your pipelines, and this reads and drives them.

Lets MCP clients like Claude Code, Claude Desktop or Codex see which pipelines failed, read the build log of the step that broke, and act on it — restart it, cancel a runaway, approve a blocked one, rotate a secret, fix a cron — with the irreversible operations put to a person first and the write tools switchable off entirely.

71 tools is the ceiling, not the floor: WOODPECKER_ALLOW_TOOLS=essential registers a curated eight instead, and a model picks the right tool far more reliably from eight than from 71 — see choosing which tools load.

What makes it different

It covers the whole API, not the read half. Repositories, pipelines, logs, secrets, registries, crons, organizations, users, agents, forges, the queue and the log level — 71 tools against Woodpecker 3.18.0. The point of an MCP server for a CI system is doing something about what it tells you.

Logs arrive as text. Woodpecker returns a step's output as an array of base64-encoded chunks with line numbers. get_step_logs decodes them, puts them back in order, reports the step's exit code, and returns the end of the log by default — a failing step explains itself in its last lines, and the first 4000 lines of npm ci answer nothing.

Agent tokens do not reach the model. GET /agents returns every agent's token in clear text, and that token is enough to attach a machine to the server and receive pipeline workloads with their secrets. Listing agents through this server redacts it. create_agent still returns one — that is the only way to get it — and says what it is.

It knows where this API is sharp. /version and /healthz sit outside the /api prefix that the Swagger document claims for them, so GET /api/version returns the web UI with HTTP 200 rather than a 404 (3.19 adds them under /api and 4.0 drops the root routes, so get_server_info falls back to the prefix); a repository that exists in the forge is a 404 here until it is activated; perPage above 50 is clamped without a word; a cron schedule is five fields, not six; and a secret with no event list is refused, because the defaults people expect live in the web UI, not in the API.

Requirements

  • Node.js ≥ 24
  • A Woodpecker personal access token — your user settings, "CLI and API". There are no scopes: the token carries the full authority of your account.

Configuration

VariableRequiredDescription
WOODPECKER_URLyesRoot URL of the server, e.g. https://woodpecker.example.com
WOODPECKER_TOKENyesPersonal access token from your user settings
WOODPECKER_READ_ONLYnotrue registers only the 34 read tools
WOODPECKER_ALLOW_TOOLSnoComma-separated tool names, list_* prefixes, or essential for a curated preset
WOODPECKER_DENY_TOOLSnoSame syntax; removed from whatever WOODPECKER_ALLOW_TOOLS left
WOODPECKER_INSECURE_TLSnotrue accepts self-signed certificates (scoped to this connection)
WOODPECKER_API_PREFIXnoPath of the API below the root, default /api. Crow CI 5 and later: /api/v1
ELICITATIONnofalse replaces the approval dialog with the two-call token. Not prefixed

WOODPECKER_URL is the server root, not the API root: https://woodpecker.example.com, not https://woodpecker.example.com/api. Both are accepted — the suffix is trimmed — because the Swagger page spells every example the long way.

Crow CI, a Woodpecker fork, serves its API under /api/v1 since 5.0: set WOODPECKER_API_PREFIX=/api/v1. That makes the API reachable, not identical — this server speaks the Woodpecker 3 API, and Crow ignores a few of its fields. See Crow CI.

Use `https://`. Over plain http the token travels unencrypted; the server

prints a warning unless the host is local. For self-signed certificates prefer a

proper internal CA over WOODPECKER_INSECURE_TLS.

Without configuration the server still starts and lists its tools (so registries and inspectors can introspect it); every call then fails with setup instructions instead of reaching the API. get_server_info works without a token, which makes it the first thing to call when nothing else does: if it answers, WOODPECKER_URL is right and the problem is the token.

Admin-only tools. Woodpecker inherits repository and organization permissions from the forge, and reserves users, agents, forges, the queue and the log level for instance administrators. Those tools are registered for everyone and answer 403 for accounts that may not use them; get_current_user reports which kind of account the token belongs to, and WOODPECKER_DENY_TOOLS is the tidy way to stop offering them at all.

Choosing which tools load

WOODPECKER_ALLOW_TOOLS and WOODPECKER_DENY_TOOLS take comma-separated tool names; a trailing * matches a whole family. essential is a curated preset — list_repositories, get_repository, list_pipelines, get_pipeline, get_step_logs, trigger_pipeline, restart_pipeline and cancel_pipeline — marked as such in the tool reference.

WOODPECKER_ALLOW_TOOLS=essential

WOODPECKER_ALLOW_TOOLS=list_*,get_pipeline,get_step_logs WOODPECKER_DENY_TOOLS=delete_*,pause_queue,create_user,update_user

With 71 tools this is not a nicety. Every visible tool costs context on every request, and a server that offers delete_forge next to get_step_logs is a server nobody should point at their production CI without narrowing it first.

An entry that matches no tool aborts startup and names it, so a typo cannot silently hide a tool — an absent tool is not something anyone traces back to an environment variable. A filtered tool is never registered, so it is absent from tools/list and unknown to tools/call alike, exactly like a write tool under WOODPECKER_READ_ONLY.

If you run several of these servers at once, mcp-hub is the other answer — its /hub endpoint replaces every server's tools with six meta-tools.

Installation

Claude Code
claude mcp add woodpecker-ci -- npx -y @ni-c/woodpecker-ci-mcp
Claude Desktop
{

"mcpServers": { "woodpecker-ci": { "command": "npx", "args": ["-y", "@ni-c/woodpecker-ci-mcp"], "env": { "WOODPECKER_URL": "https://woodpecker.example.com", "WOODPECKER_TOKEN": "…" } } } }

Codex
[mcp_servers.woodpecker-ci]

command = "npx" args = ["-y", "@ni-c/woodpecker-ci-mcp"] env = { WOODPECKER_URL = "https://woodpecker.example.com", WOODPECKER_TOKEN = "…" }

Docker
docker run --rm -i \

-e WOODPECKER_URL=https://woodpecker.example.com \ -e WOODPECKER_TOKEN=… \ ghcr.io/ni-c/woodpecker-ci-mcp

If your Woodpecker is only resolvable through your host's split DNS, add --dns : a container does not inherit the host's resolver configuration, and the public answer for an internal name is usually an address that does not respond.

Through mcp-hub

A client that cannot spawn a local process — ChatGPT connectors, Claude on the web, Cursor, LibreChat — reaches woodpecker-ci-mcp through mcp-hub: one container serves many stdio MCP servers over Streamable HTTP, with an OAuth 2.1 login behind a single password and long-lived tokens for the clients that cannot do OAuth. Its /hub endpoint puts every server behind six meta-tools, so one connector reaches all of them without N×tool schemas in the model's context, and it speaks both protocol revisions — a question this server asks travels through it to the person at the far end.

Its /config/mcp.json uses Claude Code's format, so the entry is the one you already have:

{

"mcpServers": { "woodpecker-ci": { "command": "npx", "args": ["-y", "@ni-c/woodpecker-ci-mcp"], "env": { "WOODPECKER_URL": "https://woodpecker.example.com", "WOODPECKER_TOKEN": "…" } } } }

allowTools and denyTools there are the hub's own per-server filter, which is not the same thing as *_ALLOW_TOOLS in env — the difference, and the mistake it invites, are in the client guide.

Tools

Read tools are always registered. 🛡 marks the ones that need an instance administrator; 👤 marks the ones that ask a person before acting, through MCP elicitation, falling back to a two-call confirm_token where the client cannot show a dialog.

Every tool declares an outputSchema and answers with structuredContent alongside the text block, so a client can use the result without parsing prose. Seventeen tools that answered with a sentence — _"Pipeline 12 was cancelled."_ — now answer with the fields as well, and the sentence stays where a reader wants it. get_step_logs keeps its rendered header-plus-log in the text and states the exit code, the line count and the output as fields.

The tools that report pushed content carry untrusted: true and source: "woodpecker" as fields; branch names, commit messages, pipeline titles and above all build logs — the raw stdout of arbitrary containers — are written b

Only the beginning is shown; read the rest in the repo