MCP stays in the studio
Agents and try tokens live with the team. Clients never install Cursor or paste Bearer tokens.
Built for Agencies
You run the agent. Clients mark on the link.
Keep MCP inside the studio. Send clients a guest link for suggestions — or an owner review link when they should approve. Multi-pass with before/after so sign-off is evidence-based.
Connect your agent
Review
Pass 2
Screenshot
Ledgerly dashboard, empty month
What to look at
Tiles reworked from your marks. Check the fixes.
Ledgerly
Overview
Accounts
Payments
Invoices
Reports
October
ExportBalance
$48,210
In
$12,400
Out
$9,870
PayeeStatusAmount
Northwind Studio
Cleared
1,200.00
Atlas Rent
Pending
3,450.00
Figma
Cleared
45.00
Prairie Payroll
Cleared
5,175.00
S1
M1
M2
M3
Drag to mark a region, or click for a point.
My marks
3
Your agent fixed 1 mark. Check each one, then verify or reopen.
-
M1 Must fix Resolved
Three stat tiles fight for attention. Make balance the big one.
Verify Reopen -
M2 Question Open
Should pending payments show here, or only cleared ones?
Answer -
M3 Nice to have Verified
Sidebar icons and labels don’t line up.
Reopen
Hints
1
Suggestions until you accept them.
-
S1 PolishAccept
Amounts aren’t tabular, so the column wobbles.
The problem
Agencies that use coding agents still collect client feedback in email and Figma threads. Clients should not need MCP, and their comments should not silently become the brief until the studio accepts them.
How ReviseMy fits
Studio connects MCP and opens create_review. Internally, designers/engineers leave authoritative marks. For clients, share a guest link (suggestions only) or the owner link when they should approve. Accept guest notes into marks when appropriate, request changes for the next pass, verify with after shots, then approve.
Built for studio + client workflows
Guest links for clients
Suggestions stay non-authoritative until the review owner accepts them into marks.
Before/after for approvals
Resolve marks with after images so client sign-off is about proof, not vibes.
Who decides stays explicit
Studio owns the brief unless you hand them the owner link. Guest eyes never flip approve by accident.
Agency checklist
Clear roles from internal build to client approval.
- Connect MCP on the studio side (try token or deploy)
- Open a review; leave internal must-fix marks first
- Send clients a guest link for suggestions — or owner link to approve
- Accept guest notes into marks only when you agree
- Request changes / verify after shots until client sign-off
Sample prompts
Try saying these to your agent after connecting MCP from the homepage.
-
“Open a review for this client deliverable and share the link with me.”
-
“Send a guest link to the client for suggestions only.”
-
“Address studio must-fix marks, attach after shots, then we will send pass two.”
FAQ
Should clients get MCP access?
Usually no. Guest or review links are enough. Keep try tokens inside the studio.
Guest link vs owner review link?
Guest = suggestions only. Owner link can mark authoritatively and approve / request changes — use when the client is the decision-maker.
How do we show what changed?
Have the agent resolve_marks with after images; reviewers verify on the board before the next client send.