What is ui-ticket-mcp and how does it work?

It's an MCP server that bridges human code review in the browser with AI-powered code fixes. You review UI code in a browser interface, and AI agents connected via MCP can automatically apply fixes to your codebase.

What environment variables do I need to set up?

PROJECT_ROOT is required and should point to your project's root directory. REVIEW_PORT is optional (defaults to 3200) and controls which HTTP port the REST API runs on.

Can I use this with a monorepo?

Yes, set PROJECT_ROOT to your monorepo root. The server will serve the REST API on the configured REVIEW_PORT so you can review and fix code across multiple packages.

How do I start the server?

Run `uvx ui-ticket-mcp@1.4.0` with PROJECT_ROOT set as an environment variable. The server communicates via stdio and exposes a REST API on REVIEW_PORT for the browser review interface.

What happens after I review code in the browser?

Review tickets are created and passed to AI agents via MCP. The agents can then read the tickets and apply fixes directly to your project files based on the review feedback.

MCP ServerSTDIOOfficialv1.4.0

ui-ticket MCP Server

Review UI code directly in the browser and let AI agents automatically fix issues via MCP. Built for developers who want human-in-the-loop code review with automated remediation.

io.github.0ics-srls/ui-ticket-mcp

Try MCP with AI models View source

Hosted URL

Local install

Transport

STDIO

Auth

1 required env var

What the ui-ticket MCP server does

How models use it and what it is built for.

Review UI code directly in the browser and let AI agents automatically fix issues via MCP. Built for developers who want human-in-the-loop code review with automated remediation.

Connect to ui-ticket

Local install — runs as a subprocess.

uvx ui-ticket-mcp==1.4.0

Environment variables

Configuration this server reads at startup.

PROJECT_ROOTRequired
Root directory of the project being reviewed
REVIEW_PORT
HTTP port for REST API (default: 3200)

Resources

Where to find authoritative docs and source for ui-ticket.

Source repository

Example prompts for ui-ticket

Paste any of these into Agent Studio after connecting ui-ticket.

Start a UI review session on port 3200 for my React project
Show me the current review tickets and which ones are ready for AI fixes
Apply the suggested code changes from the latest review to my project files
Explain how to configure PROJECT_ROOT for a monorepo structure

ui-ticket MCP server — FAQ

Common questions about connecting and running ui-ticket.

What is ui-ticket-mcp and how does it work?
It's an MCP server that bridges human code review in the browser with AI-powered code fixes. You review UI code in a browser interface, and AI agents connected via MCP can automatically apply fixes to your codebase.
What environment variables do I need to set up?
PROJECT_ROOT is required and should point to your project's root directory. REVIEW_PORT is optional (defaults to 3200) and controls which HTTP port the REST API runs on.
Can I use this with a monorepo?
Yes, set PROJECT_ROOT to your monorepo root. The server will serve the REST API on the configured REVIEW_PORT so you can review and fix code across multiple packages.
How do I start the server?
Run `uvx ui-ticket-mcp@1.4.0` with PROJECT_ROOT set as an environment variable. The server communicates via stdio and exposes a REST API on REVIEW_PORT for the browser review interface.
What happens after I review code in the browser?
Review tickets are created and passed to AI agents via MCP. The agents can then read the tickets and apply fixes directly to your project files based on the review feedback.

Skip the local setup — run MCP in your browser

MCP Playground runs 10,000+ hosted MCP servers — GitHub, Linear, Notion, Stripe, Sentry and more — across Claude, GPT, Gemini, DeepSeek and 60+ AI models. Compare model answers side-by-side, save agent presets, share runs. Zero install.

Open Agent Studio