Productboard MCP honesty matrix — features / initiatives / feedback / comments / status inside Productboard vs FDT create_github_issue / file:line
Productboard's MCP Server page (productboard.com/integrations/mcp-server/) markets using any agent to access and update Productboard data — "add new features, reschedule an initiative, or start building off a product specification." The server URL is https://mcp.productboard.com (HTTP + OAuth). Support ("Create and manage entities with an AI agent", updated September 4, 2026) and release notes spell out create/update for objectives, initiatives, key results, components, features, subfeatures, companies, and users; writable driver fields (Value, Risk, Impact, Confidence, Effort); relationship management (link features to initiatives, initiatives to objectives); plus comments and entity status updates on specs. The marketing overview also lists feedback and documents among entities agents can create and update.
That is a real product-management write surface inside Productboard — features, initiatives, feedback, comments, status, and prioritization fields — and it is not a ship-to-code surface. Nothing on the integrations page, support create/manage article, or connect-a-coding-agent docs publishes create_github_issue, create_pr, open_pr, a codebase/git write, or React component file:line as a Productboard MCP tool. Pulling a Productboard spec into a coding agent so that agent can write code is the agent's git workflow, not a Productboard MCP create_pr. Feedback DevTools foils with first-party create_github_issue / create_tracker_issue / mark_feedback_resolved plus capture-time source maps (component + file:line) in the ticket body, handed to your local agent. We do not claim server-side auto-opened or auto-merged PRs. Zero Productboard product integration ships in FDT today. Distinct from Great Question#85 (create_*_study + candidates), Condens#84 (read-only Artifacts), Pendo#80 (Listen/Ideas/Guides writes), and Canny#72 (Ideas/Feedback CRUD) — do not reopen Great Question#85 / Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / Pendo#80 / Canny#72.
Feedback DevTools is our product. Productboard MCP capabilities sourced from https://www.productboard.com/integrations/mcp-server/ (server https://mcp.productboard.com), https://support.productboard.com/hc/en-us/articles/54112373430931-Create-and-manage-entities-with-an-AI-agent (updated September 4, 2026), Connect a coding agent / Best practices for engineers (comments + status), and Productboard Release Notes (MCP create/edit entities) — lastChecked September 30, 2026 ~16:25pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Productboard MCP
| Feedback DevTools | Productboard MCP | |
|---|---|---|
| MCP write surface | create_github_issue / create_tracker_issue / mark_feedback_resolved — GitHub/Linear tickets with source-mapped body | Create/update features, subfeatures, initiatives, objectives, key results, components, companies, users, feedback, documents; comments + status; driver fields (Value/Risk/Impact/Confidence/Effort); relationships — inside Productboard |
| create_github_issue / create_tracker_issue | Yes — first-party MCP tools open GitHub/Linear tickets | No — published Productboard MCP writes Productboard entities (features/initiatives/feedback/comments/status), not GitHub/Linear issues |
| create_pr / open_pr / git write | No server-side auto-PR claim — local agent opens PRs from the source-mapped ticket | No create_pr / open_pr / codebase / git write on Productboard MCP — coding agents may pull specs then use their own git tools |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — published tools create/update Productboard entities and comments/status; they do not open or merge GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line in ticket body | Specs, features, initiatives, feedback, comments, status — product hierarchy evidence, not React component file:line |
| Productboard in FDT today | Zero — no Productboard product integration ships in Feedback DevTools today | First-party Productboard MCP (https://mcp.productboard.com, OAuth) into workspace entities |
| Plan gate | Free plan forever + Pro $9/mo per project — MCP ticket tools without a Productboard Spark/workspace SKU | Productboard workspace MCP (Spark-enabled workspaces per support) — not a published $9 MCP SKU (sources: integrations/mcp-server + support) |
Capability claims verified against Productboard's published MCP integrations page + support create/manage + connect/best-practices articles (lastChecked September 30, 2026 ~16:25pm Asia/Jerusalem). Spec-into-coding-agent is Productboard's delivery story; create_pr / file:line are not published Productboard MCP tools.
Where Productboard MCP is genuinely strong
Credit where due — Productboard MCP is a real PM unlock if:
- You already run Productboard (Spark) and want Claude, ChatGPT, Cursor, Codex, or Copilot to create/update features, initiatives, objectives, key results, and feedback without leaving the AI client.
- Driver-field scoring (Value, Risk, Impact, Confidence, Effort), relationship linking (features↔initiatives↔objectives), comments on specs, and status updates matter more than React component file:line.
- Pulling the latest Productboard specification into a coding or prototyping agent so delivery starts from the PM's current spec is the job — not opening GitHub/Linear tickets from the Productboard MCP itself.
Where Feedback DevTools is more honest about create_* / ship
- Features/initiatives/feedback writes are real — and they are not ship-to-code. Integrations page + support create/manage (lastChecked September 30, 2026 ~16:25pm Asia/Jerusalem) publish create/update for features, initiatives, feedback, comments, status, and driver fields inside Productboard. Neither page publishes create_github_issue, create_pr, or file:line as a Productboard MCP tool.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. Productboard's published MCP surface writes Productboard entities — a GitHub issue or PR, if any, is a separate coding agent after it pulled a spec, not a Productboard MCP tool.
- Local-agent path. The same source map is handed to your coding agent; a PR, if any, is that agent's git workflow. FDT does not claim server-side auto-open or auto-merge.
- Capture-time source maps. Every item pins the React component and file path:line so the agent starts from a known path instead of a Productboard feature ID or initiative link alone.
- Not the Great Question / Condens / Pendo / Canny foils. Great Question#85 is create_*_study + candidates. Condens#84 is read-only published Artifacts. Pendo#80 is Listen/Ideas/Guides/Orchestrate writes. Canny#72 is Ideas/Feedback CRUD on Canny. Productboard's honesty gap is PM entity CRUD (features/initiatives/feedback/comments/status) without create_github_issue / create_pr / file:line — do not reopen Great Question#85 / Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / Pendo#80 / Canny#72.
- Zero Productboard in FDT today. This foil is honesty about surfaces — Feedback DevTools does not ship a Productboard connector; it ships create_github_issue / create_tracker_issue + local-agent file:line.
Pricing shape (not the foil) (as of September 30, 2026)
- Productboard: workspace MCP (features/initiatives/feedback/comments/status writes; Spark-enabled per support) — not a published $9 MCP SKU (sources: productboard.com/integrations/mcp-server; support create/manage entities)
- Feedback DevTools: Free (unlimited collection) · Pro $9/mo per project (source: feedback-devtools.com/pricing)
MCP honesty is about capability claims, not sticker shock — FDT Pro is $9/mo per project vs Productboard as a product-management suite whose MCP creates/updates entities inside Productboard but does not publish create_github_issue / create_pr / file:line.
Who should pick which?
- Choose Productboard MCP if your job is creating/updating features, initiatives, feedback, comments, and status (plus driver scoring and hierarchy links) from Claude, ChatGPT, Cursor, or Codex, and/or pulling Productboard specs into a coding agent.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, first-party MCP tools that create GitHub/Linear tickets (create_github_issue / create_tracker_issue), and a local-agent fix path — without reading Productboard feature/initiative CRUD as a GitHub write or a source map.
Frequently asked questions
What can Productboard MCP create and update?
Per https://www.productboard.com/integrations/mcp-server/ and https://support.productboard.com/hc/en-us/articles/54112373430931-Create-and-manage-entities-with-an-AI-agent (updated September 4, 2026; lastChecked September 30, 2026 ~16:25pm Asia/Jerusalem): create and update objectives, initiatives, key results, components, features, subfeatures, companies, and users; write names/descriptions/owners/teams/statuses/custom driver fields (Value, Risk, Impact, Confidence, Effort); manage relationships (features↔initiatives↔objectives); plus comments and status on specs. The integrations overview also lists feedback and documents. Server: https://mcp.productboard.com. No invent beyond those published capabilities.
Can Productboard MCP create GitHub issues or pull requests?
No create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write / file:line on the Productboard MCP surface (productboard.com/integrations/mcp-server + support create/manage + connect/best-practices; lastChecked September 30, 2026 ~16:25pm Asia/Jerusalem). Writes are Productboard features, initiatives, feedback, comments, and status. A coding agent that pulled a Productboard spec may open a PR with its own tools — that is not a Productboard MCP create_pr. Feedback DevTools foils with create_github_issue / create_tracker_issue + source-mapped body and does not claim server-side auto-open or auto-merge. Distinct from Great Question#85 / Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / Pendo#80 / Canny#72.
Is this the same foil as Great Question MCP (#85), Pendo MCP (#80), or Canny MCP (#72)?
No. Great Question#85 is create_*_study + candidates R/W. Pendo#80 is Listen/Ideas/Guides/Orchestrate writes inside Pendo. Canny#72 is Canny Ideas/Feedback CRUD. This strip foils Productboard features/initiatives/feedback/comments/status writes inside Productboard — still no create_github_issue / create_pr / file:line. Do not reopen Great Question#85 / Condens#84 / Optimal#83 / UserTesting#82 / Lyssna#81 / Pendo#80 / Canny#72.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, not a Productboard feature/initiative writer.