Pipecd

Provides MCP integration with PipeCD to manage applications and deployments.

other

4

GitHub Stars

other

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "warashi-mcp-server-pipecd": {
      "command": "/Users/sawada/go/bin/mcp-server-pipecd",
      "args": [],
      "env": {
        "PIPECD_HOST": "demo.pipecd.dev:443",
        "PIPECD_INSECURE": "false",
        "PIPECD_API_KEY_FILE": "/Users/sawada/.config/mcp-server-pipecd/api_key"
      }
    }
  }
}

You run an MCP server to connect PipeCD with external MCP clients, enabling centralized management of applications and deployments. This server listens to an MCP client and exposes the PipeCD integration in a structured, interoperable way for automated workflows and tooling.

How to use

Configure your MCP client to connect to the PipeCD MCP server using the environment variables provided. The client should point to your PipeCD control plane, supply an API key file, and optionally relax TLS verification for testing.

How to install

Prerequisites: ensure you have a Go toolchain installed on your machine so you can install the MCP server binary from the public module path.

# Install the MCP server binary
GO111MODULE=on go install github.com/Warashi/mcp-server-pipecd@latest

# The binary is typically placed in your Go bin directory; verify it is on your PATH
which mcp-server-pipecd

Configuration example

json
{
  "mcpServers": {
    "pipecd": {
      "command": "/Users/sawada/go/bin/mcp-server-pipecd",
      "args": [],
      "env": {
        "PIPECD_HOST": "demo.pipecd.dev:443",
        "PIPECD_API_KEY_FILE": "/Users/sawada/.config/mcp-server-pipecd/api_key",
        "PIPECD_INSECURE": "false"
      }
    }
  }
}

Running the MCP server

Start the MCP server using the configuration above. Ensure the path to the binary matches where you installed it. Supply the required environment variables as part of the server process or in your process manager so the MCP client can reach PipeCD.

Additional notes

The server connects to the PipeCD control plane using the host and API key file you provide. If you need to test against a non-TLS endpoint, set PIPECD_INSECURE to true and ensure appropriate security considerations are in place.

Configuration reference

The following configuration shows how to register the PipeCD MCP server in your MCP client setup. It uses a local binary created by installing from the public module path.