Sessions, security and limits
Choose which clients can access your workspace, and recover the connection if the service stops.
Local access and trust
The MCP client runs as a local process and can act with your access to Open Canvas. Connect only clients you trust. The broker listens on loopback; it is not an unauthenticated MCP endpoint for other machines. Choose File → Pause agent access to stop MCP access to the selected workspace and its canvas. You can still edit and save in the browser.
Multiple clients and browsers
Multiple MCP client processes can attach to the same local broker when they use the same installation profile and ports. A browser tab registers with the local service. Up to eight browser tabs can be connected; choose a specific canvas before reading or editing so the agent targets the intended tab.
The broker keeps one owner for browser connections. If it stops, connected tabs reconnect when the service returns. Keep the existing browser workspace open and restore the intended local service if needed. Then call list_canvases, select the intended canvas, and read its current state and persistence status. A request that was already dispatched may have completed even if its response was lost, so inspect state before deciding whether to repeat an edit.
Page activity and limits
The editor shows page activity while a page-targeted agent call is pending. Navigating to another page hides activity for the previous page; returning shows it again only while that request is still pending. The indicator means an active request, not that work succeeded or was saved. Check the response and persistence status.
MCP requests and responses are limited to 12 MB and 30 seconds. The editor does not merge concurrent edits or automatically retry a mutation. Use JSON backups for large workspaces and inspect state after an uncertain result.
Written for Open Canvas 0.8.0