pb_feature_listLABSCO SUMMARY
Roadmap work that does not start with finding the right board.
The parts of Productboard that are slow by hand — pulling the whole product hierarchy, filing a customer note against a feature, moving a release status — become single calls, which is what lets an agent go from a support conversation to a logged note without a handoff.
What it is
An MCP server over the Productboard API, authenticated with a workspace API token. Twenty-one tools spanning the feature hierarchy, customer notes, the objective and key-result layer, and release planning.
What you get
- Features listed with filtering, read by ID, created, updated and deleted
- Products listed and created, and the full product hierarchy fetched in one call
- Customer notes listed and created
- Objectives listed, created and updated
- Key results listed, created and updated
- Releases listed, created and updated, with status changes and the release timeline
Requirements
A Productboard API token in the environment. The one-click path is the .mcpb bundle from the releases page — drag it into Claude Desktop under Developer → Extensions → Install and set the token in the extension settings; it is self-contained, with no cloning or building. If you install manually instead, turn the log level down to errors only: MCP talks over stdio, and info-level logs printed to stdout will lock the server up. There is no npx path yet.
Setup effort
Build from source — git clone https://github.com/Enreign/productboard-mcp.git
USE CASES
01
Getting the lay of the land
Fetch the full product hierarchy, then list the features under the part you care about.
02
Turning customer feedback into something the roadmap can see
Create the note, then create the feature it argues for.
03
Checking whether the quarter is on track
List the objectives and their key results, and update the ones that have moved.
04
Planning what ships next
List the releases, read the timeline, and create the one that is missing.
05
Moving a release along
Update the release, then change its status.
06
Clearing out a feature that will never be built
Read it by ID to be sure, then delete it.
21 tools
Listed in project docs. Your client may show a different list.
pb_feature_getpb_feature_createpb_feature_updatepb_feature_deletepb_product_listpb_product_createpb_product_hierarchypb_note_listpb_note_createpb_objective_listpb_objective_createpb_objective_updatepb_keyresult_listpb_keyresult_createpb_keyresult_updatepb_release_listpb_release_createpb_release_updatepb_release_status_updatepb_release_timelineBEFORE YOU INSTALL
What to know first
Tools you get
21 tools named in the project's documentation.
Requires
PRODUCTBOARD_API_TOKEN in your environment
Optional
- PRODUCTBOARD_OAUTH_CLIENT_ID in your environment
- PRODUCTBOARD_OAUTH_CLIENT_SECRET in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
# 1. Clone the repo
git clone https://github.com/Enreign/productboard-mcp.git
cd productboard-mcp
# 2. Install dependencies and build
npm install --include=dev
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"productboard": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PRODUCTBOARD_MCP>/dist/index.js"
],
"env": {
"PRODUCTBOARD_API_TOKEN": "<YOUR_PRODUCTBOARD_API_TOKEN>",
"LOG_LEVEL": "error"
}
}
}
}PRODUCTBOARD_OAUTH_CLIENT_ID and PRODUCTBOARD_OAUTH_CLIENT_SECRET are only for the optional OAuth2 sign-in; the API token in this block is the default. To use OAuth2, set PRODUCTBOARD_AUTH_TYPE to oauth2 and add both, with PRODUCTBOARD_OAUTH_REDIRECT_URI, to the same env block.
