Supported tools
Laioutr MCP is a Laioutr-wide integration whose first tools focus on Studio. Today, your assistant can inspect existing pages and variants, discover installed sections and blocks, read schemas and style tokens, and edit page content in the live Studio document.
The current tools cover sections, blocks, static and localized props, array items, global-section references, visibility, layout order, and page SEO. Future Laioutr tools can use the same connection without changing the client setup.
Example workflows
The examples below show what happens between your prompt and the result in Studio. Tool names appear as supporting detail so you can see when the assistant discovers, inspects, and changes project data.
Update localized hero content
Update the homepage hero heading to “Summer starts here” in English and “Der Sommer beginnt hier” in German.
- DiscoverHomepage variant found
The assistant selects the project and homepage variant.
project_liststudio_list_pages - InspectHero field verified
The assistant reads the page tree, current heading, and field schema before writing.
studio_get_page_treestudio_get_component_schemasstudio_get_prop - EditTwo locale values written
One atomic mutation updates English and German without replacing other locales.
studio_set_static_props
Open the homepage in Studio and check both languages in context before publishing.
Add and rearrange page sections
Add a hero section to the top of the homepage body and move the existing promotion grid directly below it.
- DiscoverAvailable sections loaded
The assistant finds the homepage and reads the installed component catalog instead of guessing component names.
studio_list_pagesstudio_list_components - InspectLayout and hero schema checked
The assistant reads the current page tree and the selected hero component schema.
studio_get_page_treestudio_get_component_schemas - EditSection added and layout reordered
The assistant adds the hero and moves the promotion grid while preserving existing section data.
studio_add_sectionstudio_move_section
Check the homepage at desktop and mobile widths in Studio before publishing.
Add array content with a style token
Add a “Free returns” item to the homepage benefits list and use the project's primary accent color.
- DiscoverBenefits field and palette found
The assistant reads the component schema and project style tokens.
studio_get_component_schemasstudio_get_style_tokens - InspectExisting array items checked
The assistant reads the section before appending a new item.
studio_get_section - EditBenefit item added and styled
The assistant creates the array item, then writes its localized text and color token.
studio_add_array_itemstudio_set_static_props
Review the new benefit in every required language and confirm that its color matches the storefront theme.
Update localized page SEO
Set the homepage SEO title to “Summer collection” in English and “Sommerkollektion” in German.
- DiscoverHomepage variant selected
The assistant finds the page variant that owns the SEO fields.
studio_list_pages - InspectCurrent SEO values read
The assistant checks the existing localized title and description maps.
studio_get_page_tree - EditLocalized SEO title updated
The assistant merges both title values without clearing other locales.
studio_update_page_variant
Check the page metadata in Studio and confirm the result for both locales before publishing.
Current limits
The first Laioutr MCP tools focus on existing Studio content. They cannot:
- create a page or page variant;
- publish changes;
- create or detach a global section;
- edit the global-section container's own props;
- write a prop value that is bound to a query.
Laioutr also rejects moves that would break a page-scoped query or cross an unsupported global-section boundary. Ask the assistant to preserve the existing structure when it reports one of these constraints.