BugHerd MCP honesty matrix — marketing vs the published tool list
BugHerd's MCP feature page (bugherd.com/feature/mcp) pitches "your AI agent just joined the team": agents triage and resolve website feedback by making changes "directly in your codebase, CMS or design tool." You review.
The same page lists the published MCP tools — and they are BugHerd task-board operations: get_task_details, list_project_tasks / list_my_tasks / list_all_tasks, update_task, add_comment, create_task / create_project / update_project. For CMS or Figma work, BugHerd itself says to pair with Webflow MCP or Figma MCP. Feedback DevTools is honest about a narrower MCP: create_github_issue / create_tracker_issue 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. BugHerd MCP marketing and tool list sourced from bugherd.com/feature/mcp on September 22, 2026; pricing from bugherd.com/pricing (July 29, 2026) — please verify before purchase.
Feedback DevTools vs BugHerd MCP
| Feedback DevTools | BugHerd MCP | |
|---|---|---|
| Marketing claim: change codebase / CMS / design tool | No — FDT does not claim MCP edits CMS or design files; local agent writes code from file:line context | Yes — copy on bugherd.com/feature/mcp: changes "directly in your codebase, CMS or design tool" |
| Published MCP tools | get_feedback_context, list_open_feedback, list_clusters, create_github_issue, create_tracker_issue, mark_feedback_resolved… | get_task_details · list_project_tasks · list_my_tasks · list_all_tasks · update_task · add_comment · create_task · create_project · update_project (+ list/get project helpers) |
| MCP tools that write CMS / Webflow / Figma | No | No — pair BugHerd MCP with Webflow MCP or Figma MCP (their designer workflow copy) |
| MCP tools that open GitHub / Linear tickets | Yes — create_github_issue (#57) + create_tracker_issue Linear (#59) with component + file:line in the body | No dedicated tracker-create tools in the published list — BugHerd board + optional PM sync (e.g. Jira two-way) |
| Source map on capture (component + file:line) | Yes — pinned at collect time for the local agent | Screenshot, URL, CSS selector, browser/OS — not React component file:line |
| Who applies the code fix | Your local Cursor / Claude agent (from MCP context or Claude Code prompt) | Your AI coding agent (Cursor, Claude Code, etc.) using BugHerd task context — not a BugHerd-server PR opener |
| Auto-open / auto-merge PRs server-side | No — we do not claim server-side auto-opened or auto-merged PRs | No — BugHerd MCP updates BugHerd tasks; you review; no request_ai_pr-style server PR tool listed |
| Mark tasks / feedback done from MCP | Yes — mark_feedback_resolved | Yes — update_task |
| Post comments from MCP | Via tracker ticket body / local agent workflow | Yes — add_comment |
| Free plan for unlimited feedback collection | Yes — forever | No — free trial; MCP beta free for subscribers |
| Paid entry price | $9/mo per project (Pro) | $50/mo Standard (5 members) |
BugHerd MCP marketing quote + published tool list verified on bugherd.com/feature/mcp, September 22, 2026; pricing verified on bugherd.com/pricing, July 29, 2026
Where BugHerd MCP is genuinely strong
Credit where due — BugHerd MCP is a real agency workflow unlock if:
- You already live in BugHerd's Kanban and want Claude/Cursor to list open tasks, read screenshots + selectors, triage, mark done, and comment without leaving the IDE.
- Your designers are fine pairing BugHerd MCP with Webflow MCP or Figma MCP for visual fixes — BugHerd says so on the feature page.
- Cross-project status, assignee triage, and client-update drafts from the task board matter more than React file:line source maps.
- You want MCP free in beta for every BugHerd subscriber once you are on a paid BugHerd plan.
Where Feedback DevTools is different (honest foil)
- Marketing vs tools. BugHerd's page says agents change the "codebase, CMS or design tool"; the published functions are BugHerd task ops. We quote both so buyers are not surprised. FDT MCP is likewise scoped: tickets + source-mapped context — not CMS/design editors.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. BugHerd's published list has no create_github_issue equivalent.
- Local-agent path, not server-side PRs. Your Cursor/Claude agent applies the fix from FDT context. We do not claim to auto-open or auto-merge PRs on a server-side clone (contrast Usero request_ai_pr on /compare/usero-alternative).
- 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 screenshot + CSS selector alone.
- Pricing shape. Unlimited free collection; Pro is $9/mo per project. BugHerd Standard starts at $50/mo for 5 members (+$8/user).
Pricing, side by side (as of September 22, 2026)
- Feedback DevTools: Free plan ($0, unlimited feedback) · Pro $9/mo per project
- BugHerd: Standard $50/mo (5 members) · Studio $80/mo (10) · Premium $150/mo (25) · +$8/mo per extra member; MCP beta free for subscribers (source: bugherd.com/pricing; MCP: bugherd.com/feature/mcp)
MCP honesty is about capability claims, not sticker shock — but a 5-person team still pays $50/mo on BugHerd Standard vs $9/mo FDT Pro on one project ($600 vs $108/year).
Who should choose what
- Choose BugHerd MCP if your board of record is BugHerd and you want agents to triage/update that board (and you are happy pairing Webflow/Figma MCP for CMS/design edits).
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create GitHub/Linear tickets, and a local-agent fix path — without claiming MCP edits CMS/design files or auto-opens PRs server-side.
- Neither MCP is a silent auto-merge bot; both expect a human review step. The honest foil is what the published tools actually do.
Frequently asked questions
What does BugHerd MCP marketing claim?
Per bugherd.com/feature/mcp (verified September 22, 2026): agents help "triage and resolve your website feedback queue by actually making changes directly in your codebase, CMS or design tool." Tagline: "your AI agent just joined the team." You review what the AI has done.
What tools does BugHerd MCP actually publish?
The same page lists: get_task_details; list_project_tasks, list_my_tasks, list_all_tasks; list_projects, get_project_details; update_task; add_comment; create_task; create_project; update_project. Those are BugHerd project/task operations — not Webflow, Figma, or git write tools.
Does BugHerd MCP edit Webflow or Figma by itself?
No. BugHerd's designer workflow says to pair BugHerd MCP with Webflow MCP or Figma MCP so the AI can action visual feedback in those tools, then mark BugHerd tasks done.
Does Feedback DevTools auto-open or auto-merge GitHub PRs server-side?
No. Feedback DevTools MCP creates tracker tickets (create_github_issue, create_tracker_issue for Linear) and supplies source-mapped context / Claude Code prompts so your local agent can write the fix. We do not claim to auto-open or auto-merge pull requests server-side.
How does Feedback DevTools MCP foil BugHerd MCP?
FDT is honest about a different surface: capture-time component + file:line, create_github_issue / create_tracker_issue, and a local-agent path. BugHerd MCP is strong at reading/updating the BugHerd board. Marketing that implies native CMS/design/codebase writers should be read against the published tool table on bugherd.com/feature/mcp.
Collect source-mapped feedback and open GitHub/Linear tickets from MCP — free.