Name: PipeCD
Author: Warashi

LABSCO SUMMARY

The credential stays in a file, not in your client config.

That is a small design choice with a real consequence: the API key never lands in the JSON block you paste around between machines, and file permissions become the control. The demo control plane in the documented example is a public one, so you can wire it up and confirm the connection works before pointing it at anything of your own.

What it is

A small Go server that speaks to a PipeCD control plane, the continuous-delivery system, so applications and their deployments can be inspected and managed from a chat client.

What you get

Access to the applications and deployments on a PipeCD control plane you name — the server holds the connection and the API key, and the client asks in ordinary language

Requirements

Install with go install github.com/Warashi/mcp-server-pipecd@latest, which puts the binary in your Go bin directory. PIPECD_HOST names the control plane, for example demo.pipecd.dev:443. The API key is read from a file whose path goes in PIPECD_API_KEY_FILE rather than being placed in the environment directly. PIPECD_INSECURE set to true drops TLS for a control plane that does not have it.

Setup effort

One command plus a key — go install github.com/Warashi/mcp-server-pipecd@latest, then supply credentials

See installation options

USE CASES

01

Checking on a deployment without opening the console

Ask about the applications and deployments on the control plane from the client you are already in.

02

Trying it before trusting it

Point it at the public demo control plane first and confirm the connection path works.

BEFORE YOU INSTALL

What to know first

Requires

Go (for go install)
PIPECD_HOST — the host of your PipeCD control plane
PIPECD_API_KEY_FILE — full path to a file containing your PipeCD API key

INSTALLATION

Connect your client

Add the block to your client, or run the command directly.

Server setup

Configuration file

JSON

{
  "mcpServers": {
    "pipecd": {
      "command": "mcp-server-pipecd",
      "args": [],
      "env": {
        "PIPECD_HOST": "demo.pipecd.dev:443",
        "PIPECD_API_KEY_FILE": "<YOUR_PIPECD_API_KEY_FILE>",
        "PIPECD_INSECURE": "false"
      }
    }
  }
}

PIPECD_API_KEY_FILE is the full path to a file containing your PipeCD API key, not the key itself; PIPECD_HOST is your control plane's host — demo.pipecd.dev:443 is the project's example; mcp-server-pipecd is the binary go install puts in your Go bin directory ($HOME/go/bin by default); use its full path if that directory is not on your PATH

go install

TERMINAL

go install github.com/Warashi/mcp-server-pipecd@latest

PipeCD