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.
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.
- 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
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.
One command plus a key — go install github.com/Warashi/mcp-server-pipecd@latest, then supply credentials