Summary
When editing a component via the Designer MCP (through the Bridge App), some operations hang and never complete — the Bridge App shows the action as "Running…" with no green checkmark, and the bridge connection then drops. The two reliable triggers we hit:
- Creating a
link-type component prop (create_prop with type: "link") hangs every time — it appears to open the link picker in the Designer and never returns.
- After any component edit, the canvas stays parked inside the component view. Subsequent page-level element queries return 0 results, and the next heavier op hangs, until the canvas is returned to the page.
Workaround we used
- We had to use remote desktop control to manually click the green ◀ "back to page" arrow in the Designer (top-left, next to the localization globe) to un-stick the canvas before the next MCP operation would work.
open_canvas({ page_id }) reports success but does not reliably re-anchor the canvas; de_page_tool switch_page does re-anchor it.
- We avoid creating
link props via MCP entirely and set link hrefs downstream instead.
Request
It would be great to have this handled natively:
create_prop with type: "link" should not hang the bridge.
- After a component edit, the MCP should reliably return/refresh the canvas to the page context (so page queries work and the next op doesn't hang) — i.e. a working programmatic equivalent of clicking the green back arrow, without needing manual/remote intervention.
Thanks!
Summary
When editing a component via the Designer MCP (through the Bridge App), some operations hang and never complete — the Bridge App shows the action as "Running…" with no green checkmark, and the bridge connection then drops. The two reliable triggers we hit:
link-type component prop (create_propwithtype: "link") hangs every time — it appears to open the link picker in the Designer and never returns.Workaround we used
open_canvas({ page_id })reports success but does not reliably re-anchor the canvas;de_page_tool switch_pagedoes re-anchor it.linkprops via MCP entirely and set linkhrefs downstream instead.Request
It would be great to have this handled natively:
create_propwithtype: "link"should not hang the bridge.Thanks!