Designer Session
Designer tools operate on a live Designer session. They require the MCP Bridge app and an active Designer session; the Designer must be open and connected for these tools to work. This is the key difference from the data tools, which run headlessly without a session.
Each tool below lists whether it reads, writes, or both. Access is governed at the tool level, so granting a tool grants all of its actions.
Note: Every Designer tool action requires siteId in addition to the parameters listed below.
asset_tool
writeUpload an image to a site’s asset library from a public URL. In 2.0 this is the only asset action that still runs through the Designer session. All other asset and folder management (listing, updating, organizing, deleting, compressing) moved to data_assets_tool.
- Bring a remotely hosted image into a site’s assets by URL during a Designer session
- For any other asset or folder work, use
data_assets_toolinstead
designer_tool
read writeInteract with the live Designer session: read the current page, mode, branch, selected element, and breakpoints; select elements; navigate the canvas between pages and component views; and create page folders.
- Read what’s currently open or selected in the Designer
- Move the canvas to a page or component, or select an element to act on; the page id it returns feeds
data_element_tool - Read a site’s breakpoints before styling, or create a page folder
element_snapshot_tool
readCapture a visual snapshot of a Designer element for debugging and visual feedback. This lets an agent see the current state of a site and verify its own changes without publishing.
- Confirm what an element actually looks like on the canvas
- Verify that a change landed as intended before publishing