Dovetail MCP honesty matrix — Channels "feedback to code in one click" vs published workspace CRUD (no create_pr)
Dovetail's Channels 2.0 launch posts market a one-click path from feedback to shipped code: the 20 July 2026 Channels post is titled "from customer feedback to code in one click" and says Channels "takes your team from customer feedback to shipped code in one click," then "Push the full context and evidence into Claude Code or Cursor." The 14 July 2026 Sun's Out launch adds "Go from customer feedback to code in one click" and "Engineers shipping fixes without delay."
The published Dovetail MCP docs (developers.dovetail.com/docs/mcp) expose workspace/project/folder/data/doc/highlight/channel/tag tools including create_project, create_data, create_doc, create_comment, create_channel_datum, and create_tag — Dovetail workspace CRUD and context push into coding agents. There is no create_pr / open_pr / codebase / git write / GitHub ship tool on that list. Feedback DevTools is honest about a different surface: create_github_issue / create_tracker_issue / mark_feedback_resolved plus source-mapped local-agent context with file:line. We do not claim server-side auto-opened or auto-merged PRs.
Feedback DevTools is our product. Dovetail Channels "one click" marketing from https://dovetail.com/blog/suns-out-channels/ (Published 20 July 2026) and https://dovetail.com/blog/suns-out-2026-launch/ (Published 14 July 2026); published MCP tools from https://developers.dovetail.com/docs/mcp — lastChecked September 29, 2026 ~10:25am Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Dovetail MCP
| Feedback DevTools | Dovetail MCP | |
|---|---|---|
| Positioning | Capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line | Customer intelligence / Channels 2.0 — blogs market feedback→code one-click; MCP is workspace CRUD + context into Claude Code/Cursor |
| Published MCP tools | create_github_issue · create_tracker_issue · mark_feedback_resolved + local-agent file:line | create_project · create_data · create_doc · create_comment · create_channel_datum · create_tag (+ search/get/list) — no create_pr |
| Blog "one click" / ship claim | N/A — FDT does not market auto-ship; create_* tickets + local-agent path | "from customer feedback to code in one click" / "shipped code in one click" / "Engineers shipping fixes without delay" |
| Push into Claude Code / Cursor | Same capture context handed to your local agent; PR if any is that agent's git workflow | Channels: "Push the full context and evidence into Claude Code or Cursor" / send context in one click |
| create_pr / open_pr / GitHub write | No — create_github_issue + local-agent fix path (Cursor/Claude opens a PR if you ask; not a Dovetail MCP PR tool) | No dedicated create_pr / open_pr / codebase / git write / GitHub ship tool on developers.dovetail.com/docs/mcp |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — published MCP creates Dovetail workspace objects, not GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line | Customer evidence / channel themes / docs — research context, not React component file:line |
| Pricing shape | Unlimited free collection; Pro $9/mo per project | Dovetail paid plans + Channels 2.0 closed beta; MCP connector, not a separate $9 MCP SKU |
Dovetail Channels "one click" quotes verified on dovetail.com/blog/suns-out-channels/ (20 July 2026) + dovetail.com/blog/suns-out-2026-launch/ (14 July 2026); MCP tools on developers.dovetail.com/docs/mcp — lastChecked September 29, 2026 ~10:25am Asia/Jerusalem
Where Dovetail MCP is genuinely strong
Credit where due — Dovetail MCP is a real customer-intelligence unlock if:
- Your evidence archive is Dovetail projects, channels, docs, and highlights and you want AI agents to search_workspace / get_project / create_doc / create_channel_datum in the research workspace.
- Hosted Streamable HTTP at dovetail.com/api/mcp (OAuth 2.1 or API token) matches how your team already authenticates.
- Pushing Channels evidence into Claude Code / Cursor / Linear / Jira as context matters more than a Dovetail MCP create_pr tool.
Where Feedback DevTools is more honest about create_* / ship
- Blog vs docs. dovetail.com/blog/suns-out-channels/ (20 July 2026) and suns-out-2026-launch/ (14 July 2026) market "feedback to code in one click," "shipped code in one click," and "Engineers shipping fixes without delay"; developers.dovetail.com/docs/mcp publishes workspace CRUD (create_project / create_data / create_doc / create_comment / create_channel_datum / create_tag) with no create_pr / open_pr / GitHub write (lastChecked September 29, 2026 ~10:25am Asia/Jerusalem). We quote both so buyers are not surprised.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. Dovetail's published MCP surface creates Dovetail workspace objects and pushes context into coding agents — not a create_github_issue / create_pr / ship equivalent.
- Local-agent path. The same context is handed to your coding agent; a PR, if any, is that agent's git workflow — not a Dovetail MCP PR tool. 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 rediscovering from a channel theme alone.
- Pricing shape. Unlimited free collection; Pro is $9/mo per project.
Pricing shape (not the foil) (as of September 29, 2026)
- Dovetail: paid plans + Channels 2.0 closed beta; MCP at dovetail.com/api/mcp (sources: dovetail.com/blog/suns-out-channels/; dovetail.com/blog/suns-out-2026-launch/; developers.dovetail.com/docs/mcp)
- 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 Dovetail as a full customer-intelligence suite with MCP as a workspace connector.
Who should pick which?
- Choose Dovetail MCP if your evidence archive is Dovetail channels/projects/docs and you want AI agents to CRUD workspace objects and push Channels context into Claude Code / Cursor / Linear / Jira.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create GitHub/Linear tickets (create_github_issue / create_tracker_issue), and a local-agent fix path — without reading Channels "feedback to code in one click" copy as a published create_pr / GitHub write tool.
Frequently asked questions
What do the Dovetail Channels 2.0 blogs claim about feedback to code?
Per https://dovetail.com/blog/suns-out-channels/ (Published 20 July 2026): titled "from customer feedback to code in one click"; "takes your team from customer feedback to shipped code in one click"; "Push the full context and evidence into Claude Code or Cursor." Per https://dovetail.com/blog/suns-out-2026-launch/ (Published 14 July 2026): "Go from customer feedback to code in one click"; "Engineers shipping fixes without delay." (lastChecked September 29, 2026 ~10:25am Asia/Jerusalem).
Which create_* tools does Dovetail MCP publish?
Per https://developers.dovetail.com/docs/mcp: workspace/project/folder tools include create_project and create_folder; data/doc/highlight tools include create_data, create_doc, create_comment, create_transcript_highlight; channels include create_channel_datum; tags include create_tag / apply_tags. Hosted endpoint https://dovetail.com/api/mcp. No create_pr / open_pr / GitHub write on the published list.
Does Dovetail MCP create pull requests or ship code fixes?
No create_pr / open_pr / codebase / git write / GitHub ship tool is on the published MCP tool list (developers.dovetail.com/docs/mcp; lastChecked September 29, 2026 ~10:25am Asia/Jerusalem). A PR or code fix, if any, is the coding agent (Claude Code / Cursor) using Dovetail context — not those MCP tools. Feedback DevTools foils with create_github_issue / create_tracker_issue + local-agent path and does not claim server-side auto-open or auto-merge.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, no server-side auto-PR or "feedback to code in one click" MCP claims.