Build from the latest spec without leaving your editor

Overview

Cursor connects to Productboard through the Productboard MCP server, giving the agent in your IDE direct access to your team’s latest product specifications. Pull the current spec for any feature or initiative, turn it into an implementation plan, and send questions and status updates back to Productboard as you build.

In addition to accessing product specs, Cursor can also access and maintain other data across your Productboard workspace. Work that used to require a separate trip to Productboard can now happen right from where you’re building.

Build from the current spec

Retrieve the live specification for any feature or initiative, or any document, straight from Productboard. When a PM updates a spec, the next pull gets the latest version, so the agent never builds from a stale copy.

Turn a spec into an implementation plan

Ask Cursor to convert a Productboard spec into a technical design document, sequenced development tasks with acceptance criteria, or identify a list of questions to resolve before writing code.

Ask questions where PMs will see them

A clarifying question posted from the editor lands as a comment on the Productboard spec. The spec owner answers in Productboard, and the answer is there for everyone who reads the spec next.

Report progress back

As implementation progresses, make updates to a feature’s status or adjust other fields as required. Edit specs and documents directly from the coding session. Productboard stays current with what’s being built.

Create and connect product entities

Create and edit features, subfeatures, initiatives, releases, objectives, key results, customer feedback, documents, and more — right from Cursor. Cursor can also update prioritization data, effort estimates, release dates, and other data fields on product entities.

Setup

A Productboard workspace admin enables the MCP Server once, under Settings → Integrations → MCP server, and chooses which roles may connect. Each product maker then connects their own agent and signs in with their existing Productboard login.

In Cursor:

1. Add the Productboard server to Cursor’s MCP configuration file (mcp.json):

   {
     "mcpServers": {
       "productboard": {
         "type": "http",
         "url": "https://mcp.productboard.com"
       }
     }
   }

2. The first time you use the connection, complete the browser sign-in with your existing Productboard login. There are no API keys to manage.

The connection acts as you. Cursor sees the same product data you can see in Productboard, and every action respects your workspace role and permissions.