Inline on MCP Apps hosts
Claude Desktop, claude.ai, Copilot, and similar hosts render screenshot + board views in a sandboxed iframe.
MCP Apps
Hosts that support MCP Apps render the review inline after create_review / get_review. CLI and link hosts still share review_url. The checkup loop is the same — only the surface changes.
Copying a review link out of chat breaks flow. Some hosts can host an interactive UI in a sandboxed iframe; others are CLI-only. Agents need one protocol that works for both.
create_review
returns a review; MCP Apps hosts open the inline UI.
You mark regions and approve or request changes in chat — or on the review_url if the host is link-only.
get_review
gives the agent next_action; human-only app tools never get called by agents.
Hosts that can open the review inline in chat via MCP Apps.
Cursor, Claude Code, and Grok still run the same loop via
review_url
—
setup guides
for every host.
Claude Desktop, claude.ai, Copilot, and similar hosts render screenshot + board views in a sandboxed iframe.
Cursor, Claude Code, Grok, and others share the secret link. Same marks, same next_action — open the URL in a browser.
add_mark, decide_review, and verify_mark power the inline UI (Visibility::App). Agents never call them — they poll get_review.
Comment threads, guest link management, drag-and-drop columns, second-opinion triage, and title edit stay on review_url / board_url.
No. Inline covers the human mark / decide loop in chat. Owner tools like guest share and rich comments still live on the full review and board URLs.
No. Those tools are human-only for the MCP App. Agents use get_review and next_action.
Start at /connectors, or jump to a host landing under /for/chatgpt, /for/claude, /for/copilot, /for/cursor, or /for/grok.