ui-ticket-mcp
Review system for UI prototypes. Humans write comments in the browser, AI agents resolve them via MCP. One process serves both MCP (stdio) and REST API (HTTP).
Setup
Add to your .mcp.json:
{
"mcpServers": {
"ui-ticket-mcp": {
"command": "uvx",
"args": ["ui-ticket-mcp"],
"env": {
"PROJECT_ROOT": "/path/to/your/project"
}
}
}
}
uvx downloads and runs the package automatically. MCP connects via stdio, REST API starts in background on http://localhost:3200. Reviews are stored in {PROJECT_ROOT}/.reviews/reviews.db (auto-created, committable to git).
Port configurable via REVIEW_PORT env var.
Fallback if you don't have
uv:pip install ui-ticket-mcp, then use"command": "ui-ticket-mcp"instead ofuvx.
MCP Tools
| Tool | Description |
|---|---|
get_review_summary() |
Summary of pages with open/resolved counts |
get_reviews(page_id?) |
List comments, optionally filtered by page |
add_review(page_id, author, text) |
Add a new comment |
resolve_review(review_id, resolved_by?) |
Mark as resolved |
reopen_review(review_id) |
Reopen a resolved review |
batch_resolve(page_id, resolved_by?) |
Resolve all open on a page |
get_pending_work() |
Open reviews grouped by page (todo list) |
find_source_file_tool(page_id) |
Find source files matching a page_id |
get_annotated_reviews(page_id?) |
Reviews with element annotation metadata |
get_setup_guide() |
Full setup guide for the review system |
REST API (starts automatically)
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/reviews/summary |
Per-page summary |
| GET | /api/reviews |
All reviews |
| GET | /api/reviews/{page_id} |
Reviews for a page |
| POST | /api/reviews/{page_id} |
Add review |
| PATCH | /api/review/{id} |
Update status/text |
| DELETE | /api/review/{id} |
Delete review |
| GET | /api/version |
Server version |
Links
- Website: uiticket.0ics.ai
- GitHub: github.com/0ics-srls/ui-ticket-mcp_public
- npm (panel): ui-ticket-panel
- npm (core): ui-ticket-core
Metadata
Release files for ui-ticket-mcp 1.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ui_ticket_mcp-1.6.0.tar.gz | 24.2 kB | Without provenance | Details for ui_ticket_mcp-1.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ui_ticket_mcp-1.6.0-py3-none-any.whl | Python 3 | none | any | Details for ui_ticket_mcp-1.6.0-py3-none-any.whl |
Total release size: 41.6 kB
Release files / ui_ticket_mcp-1.6.0.tar.gz
| Download URL | ui_ticket_mcp-1.6.0.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
603a2f60ef0d65640dec08d180d74608196649a6d6ecbe96315567fb742c8a36
|
|
BLAKE2b-256 checksum How to use checksums |
0f20f8ed1b1c52d355ceb593a6dca8b8c484e65fd2f304d72a76b43742ad3c3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / ui_ticket_mcp-1.6.0-py3-none-any.whl
| Download URL | ui_ticket_mcp-1.6.0-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87ac4344db6706b7e25bd4b1ba2838bc039ba993d84fd906a56ad156c7a58aa4
|
|
BLAKE2b-256 checksum How to use checksums |
9f673473bc0603094a5d65dcb85349d49ba2d6a4acb9c828564487f2bf2fd864
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for ui-ticket-mcp 1.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.