Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
GOCD_BASE_URL=<value> GOCD_ACCESS_TOKEN=<secret> claude mcp add io.github.sahilll15-gocd -- npx -y gocd-mcp@0.1.2Run in a terminal.
{ "mcpServers": { "io.github.sahilll15-gocd": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOCD_BASE_URL": "<value>", "GOCD_ACCESS_TOKEN": "<secret>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
An MCP server for GoCD. It exposes GoCD's REST API as MCP tools so any MCP client (Claude Code, Claude Desktop, Cursor) can read pipeline state and drive pipelines. Two implementations live here and behave identically on the wire: pick whichever fits how you want to install it.
go/ — Go implementation. Ships as a single static binary or a Docker image. Fast cold start, low memory.MCP server for GoCD: dashboard, pipelines, artifacts, agents. Context-lean output.
ts/ — TypeScript implementation. Runs on Node with no dependencies, so npx needs no build step.Both return the same context-lean output: the dashboard is summarized by default, rows are column-oriented, and responses are compact JSON. A full GoCD dashboard is several MB across many pipelines; these tools trim it to what the model needs.
Read tools (safe):
Write tools (operate):
Set GOCD_READONLY=1 to hide the three write tools. Large listings
(dashboard, pipeline_groups, materials, environments) are summarized or
filterable so they never dump the raw multi-MB body into the model's context.
Two environment variables, both required:
GOCD_BASE_URL=https://gocd.example.com
GOCD_ACCESS_TOKEN=<personal access token>
GOCD_BASE_URL is the bare host, without a trailing /go. The tools append
/go/api/... themselves. Create the token in GoCD under your profile, Personal
Access Tokens.
Zero install, nothing to build. This is the simplest way to run the server:
claude mcp add gocd -e GOCD_BASE_URL=... -e GOCD_ACCESS_TOKEN=... -- npx -y gocd-mcp
Published on npm as gocd-mcp and on the
MCP Registry as io.github.Sahilll15/gocd, so registry-aware clients can find it by name.
Download a prebuilt binary from Releases, or build it:
cd go && go build -o gocd-mcp .
Register it:
claude mcp add gocd -e GOCD_BASE_URL=... -e GOCD_ACCESS_TOKEN=... -- /path/to/gocd-mcp
claude mcp add gocd -e GOCD_BASE_URL=... -e GOCD_ACCESS_TOKEN=... \
-- docker run -i --rm -e GOCD_BASE_URL -e GOCD_ACCESS_TOKEN ghcr.io/sahilll15/gocd-mcp
To run the TypeScript source directly during development (Node >= 22.6, uses type-stripping):
cd ts && node --experimental-strip-types src/server.ts
They are functionally identical. In a local benchmark the Go build started about
4x faster (~21ms vs ~80ms cold start) and used about 6x less memory; per-request
latency was a tie because the GoCD network round-trip dominates. Prefer the Go
binary or Docker image for a spawned-per-session server; prefer npx when you want
the zero-install path and already have Node.
gocd-mcp/
├── go/ Go implementation (main.go, internal/gocd)
├── ts/ TypeScript implementation (src/server.ts source; publishes as compiled dist/server.js)
├── Dockerfile builds the Go binary into a distroless image
├── .goreleaser.yaml + .github/workflows/release.yml prebuilt binaries + ghcr image on tag
└── server.json MCP Registry manifest
© 2026 MCP Directory.
MCP server for GoCD: dashboard, pipelines, artifacts, agents. Context-lean output.
{ "mcpServers": { "io.github.sahilll15-gocd": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOCD_BASE_URL": "<value>", "GOCD_ACCESS_TOKEN": "<secret>" } } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: GOCD_BASE_URL, GOCD_ACCESS_TOKEN.
Gocd runs locally over stdio.
Last checked 2026-11-09. MCP server for GoCD: dashboard, pipelines, artifacts, agents. Context-lean output.