Pull specifications into your coding agent and send updates back. Support for Claude Code, Codex, Cursor, and more.
The Productboard MCP Server connects coding agents to your workspace over the Model Context Protocol. Agents read the specs your team writes in Productboard, ask questions as comments on the spec itself, and report progress back, so engineers build from the version you edited today. Every member signs in with their existing Productboard login, and every tool call respects workspace roles. The MCP Server is currently in beta.
Coding agents search and retrieve product documents from your workspace and pull the latest spec for any feature, initiative, or document. When you update a spec, the next agent to pull it gets your latest thinking.
Agents edit document content, post and reply to comments, and update item status and other fields as implementation progresses. A clarifying question lands on the spec where the PM will see it, and the system of record reflects build decisions as they happen. Agents can also create and list customer feedback.
Convert a spec into a structured implementation plan: sequenced tasks, acceptance criteria mapped to code tasks, and a list of gaps to resolve before writing code. Coding agents can also build clickable prototypes from a spec for early validation, or produce stakeholder-ready summaries from it.
Each agent connects as the member who authorized it, receives workspace and user context on initialization, and can only access what that member's role permits. Authentication is a one-time browser sign-in with the member's Productboard login; there are no API keys to manage.
Workspace admins enable the server; each member then authorizes their own coding agent.
Supported clients include Claude, Claude Code, Codex, and Cursor — any agent that supports standard remote MCP connections works. Members can disconnect their clients at any time, and admins can revoke every connection workspace-wide with Disconnect all members.
