Add to ChromeHow they compare
Both connect browser feedback to an AI coding agent, but they start with different jobs. Design Mode combines live style, text and DOM editing with comment pins and structured change exports. UI Ticket MCP centres on tickets: point at an element, describe the problem, discuss it in a thread and let an agent read, implement and resolve the feedback. Choose based on whether you need to demonstrate the intended result or manage a conversation about what should change.
Feature-by-feature
| Feature | Design Mode | UI Ticket MCP |
|---|---|---|
| Core workflow | Edit the rendered page, record exact changes and add element or region comments. Export the specification or send it to an agent. | Annotate elements or regions, write feedback and let the agent implement it. The documented product centres on reviews rather than direct visual style editing. |
| Installation and page access | Chrome or Firefox extension; no code added to the inspected app. Works on scriptable pages, not browser-protected surfaces. | Embed a Web Component using npm or a CDN script. The local setup also runs a Python MCP server and HTTP API; SSR apps need client-side loading. |
| Review conversations | Element and region comment pins, searchable Changes tab, and resolve or reopen through MCP. | Threaded replies, bug/suggestion/question/general tags, search, open/resolved filters and per-page pending-work summaries. |
| Agent hand-off | Copy or export changes without MCP, or connect through Cloud, Local or Self-hosted MCP. The agent still needs access to your source repository. | MCP tools expose review context, pending work and resolution actions. A page-name-based source-file finder suggests matching files in the configured project. |
| Where feedback lives | Comments are saved in local browser extension storage. Change exports provide a portable hand-off; the Cloud relay is not a shared ticket dashboard. | Local reviews live in a project SQLite database. The v1.5.0 changelog also documents an optional multi-project Ticket Hub with a dashboard and Docker self-hosting. |
| Cost and commercial use | Free under MIT, including commercial use subject to the licence terms. Paid agent or model usage is separate. | Published under CC BY-NC 4.0, described as free for study, research and non-commercial use. Commercial-use permission and Hub pricing were not established in the reviewed sources; check with the maintainers. Agent costs are separate. |
When to pick Design Mode
- You want to set the spacing, typography or copy yourself rather than describe the intended result in a ticket.
- You review scriptable localhost, staging or production pages without adding a review component to each app.
- You need an MIT-licensed tool for commercial work, with exports or optional MCP hand-off.
When to pick UI Ticket MCP
- Your primary job is reviewing prototypes through tagged tickets, threaded replies and an open-work queue.
- You control the app and want reviews stored with the project, or want to evaluate its optional multi-project Ticket Hub.
- Your use fits its non-commercial licence, or you have separately obtained the permissions needed for commercial use.
Honest take
UI Ticket MCP has a stronger documented ticket-discussion workflow: tags, reply chains and a project-level queue are useful when feedback needs clarification before implementation. Design Mode is the better fit when you want to show the exact visual change, work without modifying the app, or use a permissively licensed tool commercially. Both can mark feedback resolved; neither status proves the resulting code is correct. Review the source diff and rendered result before accepting a fix.
Sources and scope
Sources checked 14 September 2026. Documentation comparison of the official site, public README, licence and changelog through v1.6.0, checked against Design Mode's implementation. UI Ticket MCP was not installed or hands-on tested. The site lists 11 MCP tools while the README lists 10; tool count is not used as a differentiator. Hub support comes from the newer changelog, not the README's local-only setup description.