ProductBrain

io.github.moxzasv0.1.0更新于 Oct 9, 2026

Drive your ProductBrain product plan (goals, needs, bets, jobs) from any MCP client.

已验证STDIO仅桌面Developer Tools Productivity & Workflow

概览

AI 生成的概览

让助手搜索、读取和修改 ProductBrain 产品计划（目标、需求、下注、任务），并驱动其实时画布。

功能: 它是 ProductBrain 版本化 v1 REST API 的轻量传输层，每个面向代理的端点对应一个工具。工具涵盖语义搜索、节点批量读取、树状上下文、节点与阶段变更、迭代列表、故事映射方法论工作流、OKF 导出以及计划变更日志。它还能驱动或读取实时画布，并管理项目、Webhook、分享链接、成员、代理席位和套餐状态。
适用场景: 当团队把产品计划放在 ProductBrain，并希望助手在聊天客户端中查询内容、提出或执行计划变更、运行故事映射方法论，或管理项目、Webhook 和分享链接时，适合使用。
运行要求: 通过 npx 以 stdio 方式在本地运行 npm 包 @productbrain-com/mcp，因此需要 Node.js。需要在 PRODUCTBRAIN_API_KEY 中提供 ProductBrain API 密钥（应用 API Keys 设置中的 pb_ 密钥；免费套餐也包含 API 访问）。PRODUCTBRAIN_PROJECT_ID 可选，PRODUCTBRAIN_API_URL 默认指向托管 API。仅支持桌面客户端。

安装前请注意

API 密钥属于机密，可访问你的计划。mutate 可创建、更新和删除节点与阶段，项目工具可归档项目；Webhook 与分享链接工具可注册端点或生成公开只读链接，且 create_webhook 与 add_agent_seat 返回的签名密钥或密钥仅显示一次。部分工具仅限 Team 套餐。计划数据会发送到 ProductBrain 的托管 API。

安装

在 SourceWeft 中

打开控制台中的 ProductBrain，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

ProductBrain MCP server

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.

Design — a thin shim, on purpose

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:

It's stable when the MCP spec churns — the contract you depend on is the frozen v1 API, not the protocol.
You can drop to raw HTTP or bring your own LLM at any time; MCP is one front-door, not the only one.
Responses carry the same in-band _meta coaching the API returns, so your agent self-corrects.

Install

jsonc

// 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 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"      }    }  }}

bash

# Claude Codeclaude mcp add productbrain \  -e PRODUCTBRAIN_API_KEY=pb_your_key \  -e PRODUCTBRAIN_PROJECT_ID=your-project-id \  -- npx -y @productbrain-com/mcp

# Claude Codeclaude 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.

Config (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`

Tools

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

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.

Source, licence, registry

Source: https://github.com/moxzas/productbrain-mcp (MIT). Issues and pull requests welcome there.
npm: @productbrain-com/mcp. Every release is published from the repository's tag of the same version.
MCP registry name: io.github.moxzas/productbrain (server.json in this repo is the registry manifest).
The server sends User-Agent: productbrain-mcp/<version> so you can tell MCP traffic from raw REST calls in your own logs.

Proving it works

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:

bash

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

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.

来源：README.md，提交 501f630

工具

工具元数据尚未被收录。

版本历史

v0.1.0最新Oct 9, 2026