Beta notice
Productboard MCP Server is currently in Beta. Use it for experimentation, prototyping, and early integrations. We're actively looking for Feedback & Help – let us know what works and what doesn't.
The Productboard MCP server lets your coding agent read product specs straight from Productboard — and write back to them. No copy-pasting, no stale context, no guessing whether the spec in your terminal matches the one your product manager just edited.
This guide is for engineers and product operations managers. It assumes you've used a coding agent before.
Before you start
You'll get value from the MCP server fastest if two things are true:
- You have specs worth pulling. The server delivers specs to your agent — it can't deliver what hasn't been written yet.
- Your coding agent supports remote MCP servers. Claude Code and Cursor are tested and documented here. Other MCP-compatible clients should work too.
Write your specs first
The MCP server is the delivery path for specs you author in Spark. So the first step happens inside Productboard, not your terminal. For the full walkthrough, see Write product specifications with Spark.
A clear, current spec in Productboard is what makes everything below work. The sharper your spec, the better your agent's output.
Connect your coding agent
Connect to Claude Code, Cursor, and more.
Find out more about Connecting your agent
What your agent can and can't do
Your agent connects as you. It sees the same specs you can see in Productboard, and nothing more. The connection respects your existing permissions, so there's no way for an agent to reach content you don't already have access to.
Once connected, your agent can:
- Find specs — search by the name of the initiative/feature/sub-feature, or who owns it, or how it's tagged.
- Read specs — pull the full, current content of any spec it has access to.
- Refine specs — propose and apply edits to spec content, keeping Productboard up to date as decisions get made.
- Ask questions — read and post comments on a spec, so a clarifying question lands with the spec owner instead of getting buried in code.
- Report progress — update an item's status to reflect where the work stands.
A few good habits:
- Start a request with "use productboard…" so your agent knows to reach for the connection — for example, "Use productboard to show me the spec for the comments API."
- Refer to specs by name, not ID. "the notifications spec" works better than a long identifier.
- Remember the agent is reading and writing real Productboard content. Comments and status changes notify your teammates, so treat them as you would any other update.
For more ideas, see Workflow and prompts