ReviseMy
How it works For agents FAQ Try with your agent GitHub ↗

Visual feedback
with your agent.

Human-in-the-loop design review for agents. Capture UI, websites, slides, or email from a screenshot, URL, PDF, or HTML; mark what matters; track fixes on the board; and send clear next steps back over MCP on Laravel Cloud

ReviseMy review — mark feedback on a capture, then approve or request changes

One feedback loop for anything visual

From capture to approval, ReviseMy keeps reviews, marks, guest feedback, and lifecycle together — so nothing gets lost between passes.

Capture anything visual

Ask your agent to open a review from screenshots, a page URL (desktop + mobile), PDF slides, or email HTML — each type gets its own checklist and vision lens.

Second opinion

Optional hints can land first — checklist immediately, optional Claude or OpenAI vision when a key is set. Useful suggestions, never decisions.

Precise marks

Open the review link, point or outline the exact area, set must-fix / nice to have / question / keep, and keep a threaded comment on each mark.

Guest eyes

Share a private guest link when you want another set of eyes — no accounts. Your marks stay authoritative.

Board to done

Track marks from open → resolved → verified on the board. Agents can attach before/after evidence when they fix something.

Approve and loop

Approve or request changes. Structured next steps return over MCP — repeat until it feels right.

Try saying: “Run a design checkup,” “review this URL,” or “address my feedback.” ReviseMy handles the MCP handoff inside the agent workflow you already use.

The technical handoff

create_review accepts images, a capture URL, PDF, or HTML. When you finish, get_review returns work packets and one clear next_action: wait, apply marks, open another pass, or stop. In MCP Apps hosts, the review renders inline in chat; CLI hosts still use the review_url link.

  • Marks include intent and priority: must-fix, nice to have, question, or keep
  • second_opinion and guest findings stay suggestions until you accept them
  • resolve_marks can close marks with notes and optional before/after evidence
  • Requesting changes links a follow-up pass via create_review + parent_id
  • The MCP prompt design_checkup_loop can guide the full cycle

Try it with your agent

Choose the app you already use. Try free — no account required — and connect ChatGPT, Claude, Copilot, Cursor, or Grok. Any MCP client can use the same URL and Bearer token; see Connectors for the full host list.

FAQ

Short answers on hosts, links, marks, passes, and sharing.

Got a link — where’s the inline review?

You always get a review_url. Open it, mark, approve — works everywhere. On MCP Apps hosts (Claude web/Desktop, Copilot, …) the same review can also show up inline in chat. Cursor, Claude Code, and Grok are link-only for now — same loop, just in a tab.

Do I need to sign up?

Nope. Grab a free try token in Try with your agent, paste the MCP config, and go — no ReviseMy account.

My marks vs second opinion vs guest — who’s in charge?

You. M# marks are the brief — that’s what the agent should fix. S# second opinion and G# guest notes stay suggestions until you accept them.

What can my agent send?

One source per review: screenshots, a live URL (desktop + mobile captures), a PDF deck, or email HTML. See how it works for the full loop.

What does the agent do after I decide?

Poll get_review and follow next_action: wait while you mark, fix your pins and spin up the next pass, or stop when you approve.

What’s the board — and what’s a pass?

The board is your checklist: each mark moves open → resolved → verified. Request changes and your agent fixes what you marked, then uploads fresh captures for pass 2 (and on). Agents can attach before/after shots when they resolve a mark — you verify when it actually looks right.

Can I share a review with someone else?

Yep. Your review link is secret — anyone with it can mark and decide. Need a teammate or client? Use Share to copy or regenerate a guest link (suggestions only; your marks still run the show). Set expiry to 7 days (default), 14 days, never, or a custom date.

Shipped, not finished

ReviseMy sat as a side project on the back burner since September 2024 — an idea and a Figma file, because I love giving design feedback. Not to be a dick, but to be a Derek. Then Taylor Otwell’s Laravel Cloud weekend challenge was the nudge to ship an MCP on Laravel.

Built in a weekend on the side — it passes tests, and of course it can still be improved. Curious what you think; any feedback is welcome.

“Best side project shipped on Laravel Cloud this weekend… reply with a laravel.cloud URL.” GAME ON. ↗

Email me at derekj@hey.com or DM me on X at x.com/heyderekj.

Open source on GitHub — code, issues, and PRs welcome. View on GitHub ↗