Ui Ticket Mcp
Capture UI review feedback in the browser and hand structured tickets to your coding agent so fixes happen in-repo without copy-pasting screenshots.
Overview
ui-ticket-mcp is a MCP server for the Ship phase that connects in-browser UI review to your coding agent so humans flag visual issues and AI applies fixes in the repo.
What is this MCP server?
- Human-in-the-browser UI review linked to MCP agents that edit project code
- stdio PyPI package ui-ticket-mcp v1.4.0 with configurable REVIEW_PORT REST API (default 3200)
- Requires PROJECT_ROOT so the agent works against the correct repo tree
- Designed as a human-to-AI code review bridge rather than a static linter
- Package version 1.4.0
- Transport stdio via PyPI identifier ui-ticket-mcp
- REVIEW_PORT defaults to 3200 for REST API
Community signal: 8 GitHub stars.
What problem does it solve?
Visual UI feedback often dies in screenshots and chat while agents lack structured tickets tied to the actual project root.
Who is it for?
Indie builders shipping web UIs who already use MCP agents and want a dedicated review-to-code pipeline without building a custom ticketing UI.
Skip if: Teams that only need automated accessibility or unit tests with no human browser review step.
What do I get? / Deliverables
After install, reviewers work in the browser and your agent receives actionable review context scoped to PROJECT_ROOT for faster UI fix iterations.
- MCP-linked UI review session scoped to your project
- Structured human feedback consumable by the coding agent
- HTTP review API on REVIEW_PORT default 3200
Recommended MCP Servers
Journey fit
How it compares
Browser-linked review bridge MCP server, not a static code-review skill or generic test runner.
Common Questions / FAQ
Who is Ui Ticket Mcp for?
Solo and indie developers shipping web frontends with Claude Code, Cursor, Codex, or Windsurf who want humans to review UI in the browser while agents fix code via MCP.
When should I use Ui Ticket Mcp?
Use it during Ship review when layout, components, or responsive behavior need human eyes in a real browser before you merge or deploy.
How do I add Ui Ticket Mcp to my agent?
Install the PyPI package Ui Ticket Mcp, set PROJECT_ROOT (required) and optional REVIEW_PORT, add the stdio MCP entry in Claude Code or Cursor, then start your dev app and review UI against that root.