Create Accountor Login
Docs

Section and Stylesheet Tools

Part of the MountDev Ops Websites documentation. Updated November 13, 2026

MountDev Ops Websites documentation | Updated November 13, 2026

Read and change one section of a page, and a theme's stylesheet, without sending the whole page. People, API keys, and the account's own AI assistant use the same actions with the same checks.

Sections by Place

A page's sections are numbered from 0 in the tools (0 is the first section). In plain words and on screen the first section is "section 1".

  • See one section of a page (action sites.pagesection.get, MCP tool websites_page_section_get): give the page and the place. A custom section comes back with its name, HTML, CSS, and text fields. Any other section comes back with its own settings.
  • Change a custom section of a page (action sites.pagesection.save, MCP tool websites_page_section_save): give the page, the place, and any of html, css, fields, and name. What you leave out stays as it was. Only a custom section has HTML, CSS, and fields. A custom section's HTML may use the interactive pieces (theme choice, menu button, show and hide, switcher) described under Interactive Pieces in the Custom Sections page; the answer lists anything cleaning removed.
  • Add a section to a page (action sites.pagesection.add, MCP tool websites_page_section_add): give the page and the kind (for example text or custom) with that kind's settings. Add a place to put it there, or leave it out to add it at the end. A page holds at most 200 sections.
  • Move a section of a page (action sites.pagesection.move, MCP tool websites_page_section_move): give the page, the place it is now (from), and the place it should go (to). The other sections keep their order and their contents.
  • Remove a section from a page (action sites.pagesection.remove, MCP tool websites_page_section_remove): give the page and the place. The sections after it move up by one.

A place that does not exist is refused, and the answer says how many sections the page has.

What Cleaning Removes

A custom section's HTML and CSS are cleaned every time they are saved, the same way as on the screen. Scripts, event handlers, frames, forms that post elsewhere, and addresses outside the website are removed. The answer to a save lists each removal as kind (html or css), what was removed, and why, in a plain sentence, so a person or an assistant sees exactly what changed and can try again.

Stylesheet for a Theme

  • See a theme's stylesheet (action sites.theme.css.get, MCP tool websites_theme_css_get): the CSS every page of a website using the theme gets.
  • Change a theme's stylesheet (action sites.theme.css.save, MCP tool websites_theme_css_save): give the theme and the CSS (up to 100,000 characters). It is cleaned the same way, and the answer lists what was removed and why. Leave the CSS out to clear the stylesheet. It shows on the live website after the next publish.

Drafts and Publishing

Seeing a section or a stylesheet needs the permission to see websites. Changing one needs the permission to build websites (sites.edit).

A change an AI assistant or an API key saves stays a draft: the page is marked as waiting for a person, and the website does not change until a person with the publish permission publishes. An assistant never publishes. A person's change on a page already marked ready is kept as it was marked.

Every change is written in the Activity Log with who made it ("AI agent" for an assistant) and which section it changed.

Ask Us Anything

We’d love to hear from you!