Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Drive your ProductBrain product plan (goals, needs, bets, jobs) from any MCP client.
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.
PRODUCTBRAIN_API_KEY, PRODUCTBRAIN_PROJECT_ID, PRODUCTBRAIN_API_URLValues 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": {
"productbrain": {
"command": "npx",
"args": [
"-y",
"@productbrain-com/mcp"
],
"env": {
"PRODUCTBRAIN_API_KEY": "your-value",
"PRODUCTBRAIN_PROJECT_ID": "your-value",
"PRODUCTBRAIN_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add productbrain --env PRODUCTBRAIN_API_KEY=your-value --env PRODUCTBRAIN_PROJECT_ID=your-value --env PRODUCTBRAIN_API_URL=your-value -- npx -y @productbrain-com/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"productbrain": {
"command": "npx",
"args": [
"-y",
"@productbrain-com/mcp"
],
"env": {
"PRODUCTBRAIN_API_KEY": "your-value",
"PRODUCTBRAIN_PROJECT_ID": "your-value",
"PRODUCTBRAIN_API_URL": "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": {
"productbrain": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@productbrain-com/mcp"
],
"env": {
"PRODUCTBRAIN_API_KEY": "your-value",
"PRODUCTBRAIN_PROJECT_ID": "your-value",
"PRODUCTBRAIN_API_URL": "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.
PRODUCTBRAIN_PROJECT_ID envPRODUCTBRAIN_API_URL envThese 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 7, 2026
The registry name was verified with the GitHub account moxzas, 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: PRODUCTBRAIN_API_KEY
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.0) reached the registry 30 days 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, Signoff
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.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
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.
Drive your ProductBrain plan from an MCP client — Claude Desktop, Cursor, Claude Code — with tools for search, read, mutate, the methodology workflow, and the live view.
This server is a thin transport over ProductBrain's versioned v1 REST API. Each tool is one call to an existing /api/v1 endpoint. The REST contract stays canonical:
_meta coaching the API returns, so your agent self-corrects.// Claude Desktop — claude_desktop_config.json
{ "mcpServers": { "productbrain": { "command": "npx", "args": ["-y", "@productbrain-com/mcp"], "env": { "PRODUCTBRAIN_API_KEY": "pb_your_key", "PRODUCTBRAIN_PROJECT_ID": "your-project-id" } } } }
# Claude Code
claude mcp add productbrain \ -e PRODUCTBRAIN_API_KEY=pb_your_key \ -e PRODUCTBRAIN_PROJECT_ID=your-project-id \ -- npx -y @productbrain-com/mcp
Cursor and other clients: add an mcpServers entry with the same command/args/env.
| Var | Required | Default |
|---|---|---|
PRODUCTBRAIN_API_KEY | yes | — (your pb_ key from the app's API Key modal) |
PRODUCTBRAIN_PROJECT_ID | no | — (tools also accept a projectId argument) |
PRODUCTBRAIN_API_URL | no | https://productbrain.com/api/v1 |
Every agent-facing /api/v1 endpoint has a tool. One tool, one endpoint, same _meta coaching passed back verbatim.
The plan
| Tool | Maps to | Use |
|---|---|---|
search | GET /search | Semantic search — use first for any lookup |
list_nodes | GET /nodes | Bulk read, optional type/iteration filter |
get_tree | GET /tree | A node in context (ancestors/siblings/children/subtree) |
mutate | POST /mutate | Create/update/delete nodes + phases; pass idempotencyKey to make retries safe |
list_iterations | GET /iterations | Phases; current:true for the active one |
run_workflow | POST /workflow | Story-Mapping methodology (add / task-curate / phase-assign) |
export_okf | GET /export-okf | The plan as a portable OKF file bundle |
get_changelog | GET /changelog | Plan history: every add/update/delete/restore, attributed to the app or a named agent |
The view
| Tool | Maps to | Use |
|---|---|---|
set_view / read_view | POST /view-command, GET /view-state | Drive / read the live canvas |
Projects
| Tool | Maps to | Use |
|---|---|---|
list_projects | GET /projects | Projects you own or are a member of; includeArchived for the rest |
create_project | POST /mutate {addProject} | Bootstrap a brain — seeds the system "Later" phase. Pass an explicit id: addProject runs before mutate reads Idempotency-Key, so it is not retry-safe |
rename_project | POST /mutate {renameProject} | Change the display name; the id is immutable |
archive_project | PATCH /projects | Hide/unhide without deleting (reversible) |
Webhooks
| Tool | Maps to | Use |
|---|---|---|
list_webhooks | GET /webhooks | Registered hooks with lastStatus — spot a failing receiver |
create_webhook | POST /webhooks | Register; returns the signing secret once |
update_webhook | PATCH /webhooks | Change url/events in place, or rotateSecret:true. Prefer over delete+recreate |
delete_webhook | DELETE /webhooks | Remove a registration |
Share links
| Tool | Maps to | Use |
|---|---|---|
create_share_link | POST /share | Mint a public read-only link; expiresInDays for a TTL |
list_share_links | GET /share | Audit every token minted, with an active flag |
revoke_share_link | DELETE /share | Kill a leaked or stale link |
Members and budget
| Tool | Maps to | Use |
|---|---|---|
list_members | GET /members | Humans and agent seats on a project |
add_agent_seat | POST /members | Mint an agent seat; the pb_ key is returned once (Team tier) |
invite_contributor | POST /members | Passwordless guest invite, scoped to the projects you name (Team tier) |
revoke_member | DELETE /members | Remove a seat; an agent's key dies with its last membership |
tier_status | GET /tier-status | Your tier, API access, credit balance and limits — check before a large run |
submit_feedback | POST /feedback | Tell the PB team what to improve: feature requests, friction, bugs, notes |
Full API reference: https://productbrain.com/docs/llm-guide.md.
@productbrain-com/mcp. Every release is published from the repository's tag of the same version.io.github.moxzas/productbrain (server.json in this repo is the registry manifest).User-Agent: productbrain-mcp/ so you can tell MCP traffic from raw REST calls in your own logs.Two headless scripts in the repository (src/spike-proof.ts, src/parity-proof.ts; not shipped in the npm package), both run against a real deployment. Use a throwaway project on your own account:
PRODUCTBRAIN_API_KEY=pb_your_key \
PRODUCTBRAIN_PROJECT_ID=your-sandbox-project \ npm run spike # transport + auth + one read + one write
PRODUCTBRAIN_API_KEY=pb_your_key \ npm run parity # every non-plan tool once, on a throwaway project
parity creates its own throwaway project and cleans up after itself (archiving it at the end — there is no project-delete endpoint).
The Team-tier tools (add_agent_seat, invite_contributor) return 403 team_tier_required on a Builder key, and that counts as a pass — with one caveat worth knowing. It proves the shim reached the right route and passed the error and its _meta tip straight through; it does not validate the request body, because the tier gate runs before the body is read. Run parity with a Team-tier key to check those two properly.