One MCP endpoint
Same Bearer try token and `/mcp/revisemy` URL across hosts. Ask agent or Do it myself on the homepage for host-specific setup.
Try with your agent
Built for Engineers
Ship the fix, prove it, wait for a human eye.
Wire MCP once, open a review from your agent, implement marks, resolve with notes and optional after images, and poll get_review until next_action says stop.
The problem
Agents change UI in chat without a durable review artifact. Human feedback gets buried, and “fixed” claims lack before/after proof tied to specific marks.
How ReviseMy fits
Get a try token on the homepage, connect your host (Cursor, Claude, Copilot, …), call create_review with the right source, share review_url (or open inline on MCP Apps hosts). Implement pins, resolve_marks with evidence, poll get_review, and follow next_action — wait, apply marks, open another pass, or stop.
Built for the agent workflow
resolve_marks with evidence
Close each human pin with a note and optional after image so verification is concrete.
next_action is the contract
get_review returns work packets and one clear next step — no guessing whether to wait or open pass two.
Link or inline review
CLI hosts share review_url; MCP Apps hosts can render the review inline. Same marks either way.
Engineer checklist
From try token to approved pass.
- Mint a try token and connect MCP for your host
- create_review with one source (images, capture_url, html, or pdf)
- Share review_url (or open inline) and wait while humans mark
- Fix pins; resolve_marks with notes / after shots
- Poll get_review and follow next_action until approved
Sample prompts
Try saying these to your agent after connecting MCP from the homepage.
-
“Run a ReviseMy design checkup on the work I just changed.”
-
“Address my feedback — resolve each mark and attach after shots.”
-
“Open a new pass with fresh captures after I request changes.”
FAQ
Where do I get the MCP config?
Homepage Try with your agent — Ask agent pastes a filled prompt, or Do it myself copies URL, Bearer, and host JSON.
Can I review localhost UI?
Yes. Prefer screenshots as data URLs. Public staging can use capture_url + page_url.
Who verifies marks?
Humans only. Agents resolve; reviewers verify or reopen.