Link workflow
Cursor shares review_url (MCP Apps inline is for other hosts). Same tools, browser for human marks.
Try with your agent
Built for Cursor
Design checkup from Cursor
Add ReviseMy as an MCP server in Cursor. After UI work, ask the agent to run create_review — it shares a review_url for you to mark. Cursor polls get_review and follows next_action until you approve.
The problem
Cursor agents often claim UI is done from DOM or screenshots in chat. Without a human mark surface and next_action gate, “looks fine” is not a review.
How ReviseMy fits
Get a try token, add the MCP config in Cursor, then ask for a design checkup after visual changes. Open the review_url, mark what matters, approve or request changes — the agent reads structured work packets.
What you get with Cursor
Built for coding agents
create_review after UI changes; resolve_marks with notes and after shots; never verify for you.
Optional webhooks
Pass webhook_url when you want CI to gate on review.decided instead of polling — see /webhooks.
Quick setup
- Get a free try token on the homepage
- Add MCP server config in Cursor (URL + Bearer)
- Ask the agent to run create_review after UI work
- Open review_url, mark, decide; agent follows next_action
FAQ
Where is the Cursor JSON?
See /connectors#cursor and the homepage Ask agent flow after you create a try token.
Full paste-ready setup for Cursor: Connectors · Cursor · MCP Apps vs review_url