Build from the latest spec without leaving your editor

Overview

Cursor connects to Productboard over the open MCP standard, giving the agent in your editor direct access to the specs your team writes. Pull the current spec for any feature, plan implementation from it, and send questions and status updates back to Productboard as you build. A workspace admin enables the MCP Server once, and each engineer connects by adding one snippet to Cursor's MCP configuration.

Build from the current spec

Retrieve the spec for any feature, initiative, or 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 sequenced tasks, acceptance criteria mapped to code tasks, and a list of gaps 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

Update an item's status and other fields as implementation progresses, and edit specs and documents directly from the coding session. Productboard stays current with what's being built.

Setup

A Productboard workspace admin first enables the MCP Server under Settings → Integrations → MCP servers and chooses which roles may connect. Then, in Cursor:

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

   {
     "mcpServers": {
       "productboard": {
         "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 specs you can see in Productboard, and every action respects your workspace role.