mcp -pipecd

This MCP server provides an integration point for PipeCD, allowing MCP clients such as Claude to manage and synchronize models and contexts with a PipeCD control plane. The server is configured via environment variables that point to a PipeCD host, an API key, and an option to disable SSL/TLS verification. To use it, deploy the binary and supply the appropriate environment variables so clients can connect to the PipeCD control plane and authorize requests. Once running, MCP clients can query, update, and monitor application contexts and deployment information as defined by the MCP protocol and PipeCD integration.

Typical usage involves starting the server with the configured environment, then pointing your MCP client to the host where this server is exposed. The example in the repository shows how to set PIPECD_HOST to the target PipeCD API, PIPECD_API_KEY_FILE to a file containing the API key, and PIPECD_INSECURE to control TLS verification. Clients can then fetch models, push updates, and receive context changes from PipeCD through this MCP bridge.

Prerequisites:

• Go 1.18+ installed on your machine
• Access to a PipeCD control plane and a valid API key

Step-by-step installation:

1. Ensure Go is installed and in your PATH

   • Check: go version

2. Install the mcp-server-pipecd binary using go install

   • Go to your terminal and run:

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

   This will place the binary in your GOPATH/bin or, with modern Go, in ~/go/bin by default.

3. Verify installation

   • Ensure the binary exists, e.g.:

   ls -l ~/go/bin/mcp-server-pipecd

4. Prepare configuration and environment

   • Create the API key file at the path you will reference in PIPECD_API_KEY_FILE
   • Set PIPECD_HOST to your PipeCD control plane (e.g., demo.pipecd.dev:443)
   • Optionally set PIPECD_INSECURE to true if you are not using TLS/SSL

5. Run the server with the example configuration

   • Example (adjust paths as needed):

   PIPECD_HOST=demo.pipecd.dev:443 PIPECD_API_KEY_FILE=${HOME}/.config/mcp-server-pipecd/api_key PIPECD_INSECURE=false ~/go/bin/mcp-server-pipecd

6. Confirm the server is running and accessible by your MCP clients

   • Use your MCP client to connect to the configured host and verify models/contexts are retrievable.

Notes and tips:

• Ensure PIPECD_API_KEY_FILE contains a valid API key with permissions to access the PipeCD control plane.
• If you operate behind a proxy or in a restricted network, configure your environment to allow outbound connections to the PipeCD host.
• PIPECD_INSECURE should be set to true only in trusted or development environments where TLS verification is not required.
• The example uses an absolute path for the mcp-server-pipecd binary; adapt the command if you installed the binary in a different location.
• If you need to rotate API keys, update PIPECD_API_KEY_FILE accordingly and restart the server to pick up changes.
• The server acts as a bridge between MCP clients and PipeCD; consult PipeCD documentation for the exact MCP capabilities exposed (models, contexts, and update semantics).