MCP stays in the studio
Agents and try tokens live with the team. Clients never install Cursor or paste Bearer tokens.
Built for Agencies
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.
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.
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.
Agents and try tokens live with the team. Clients never install Cursor or paste Bearer tokens.
Suggestions stay non-authoritative until the review owner accepts them into marks.
Resolve marks with after images so client sign-off is about proof, not vibes.
Studio owns the brief unless you hand them the owner link. Guest eyes never flip approve by accident.
Clear roles from internal build to client approval.
Try saying these to your agent after connecting MCP from the homepage.
Usually no. Guest or review links are enough. Keep try tokens inside the studio.
Guest = suggestions only. Owner link can mark authoritatively and approve / request changes — use when the client is the decision-maker.
Have the agent resolve_marks with after images; reviewers verify on the board before the next client send.