Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for GoCD: dashboard, pipelines, artifacts, agents. Context-lean output.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GOCD_BASE_URL, GOCD_ACCESS_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"gocd": {
"command": "npx",
"args": [
"-y",
"gocd-mcp"
],
"env": {
"GOCD_BASE_URL": "your-value",
"GOCD_ACCESS_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add gocd --env GOCD_BASE_URL=your-value --env GOCD_ACCESS_TOKEN=your-value -- npx -y gocd-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gocd": {
"command": "npx",
"args": [
"-y",
"gocd-mcp"
],
"env": {
"GOCD_BASE_URL": "your-value",
"GOCD_ACCESS_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"gocd": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"gocd-mcp"
],
"env": {
"GOCD_BASE_URL": "your-value",
"GOCD_ACCESS_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account Sahilll15, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GOCD_BASE_URL, GOCD_ACCESS_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Winecellarbuilders
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find the team for your wine room.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.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):
| Tool | What it does |
|---|---|
gocd_dashboard | Dashboard health. No args = summary; filter/status/detail drill down |
gocd_pipeline_status | Paused / locked / schedulable for one pipeline |
gocd_pipeline_instance | One run: stages with per-job result, plus trigger |
gocd_pipeline_history | Recent runs for one pipeline. Optional limit |
gocd_stage_instance | One stage run with per-job state and agent |
gocd_stage_history | Recent runs of one stage |
gocd_compare | What changed between two runs: commits per material |
gocd_list_artifacts | A job's artifact files as [path, url] |
gocd_get_artifact | One artifact file, tail-capped (cap_kb) to stay context-lean |
gocd_list_agents | Build agents and state. Optional filter, limit |
gocd_get_agent | One agent by uuid |
gocd_materials | Configured materials. Optional filter |
gocd_environments | Environments and their pipeline/var counts |
gocd_pipeline_groups | Pipeline groups. Filter to list a group's pipelines |
gocd_server_health | Server health messages, counted by level |
gocd_version | GoCD server version |
Write tools (operate):
| Tool | What it does |
|---|---|
gocd_trigger_pipeline | Schedule a pipeline run |
gocd_pause_pipeline | Pause a pipeline |
gocd_unpause_pipeline | Resume a pipeline |
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=
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