Reference/MCP server
Structure tools
These MCP tools shape the skeleton of your docs: the sections that appear as tabs on your site and the collections that group articles in the sidebar. As with all Clayo tools, you describe the reorganization you want and your agent handles the calls.
For the concepts behind the hierarchy, read Organize with sections and collections first.
At a glance
| Tool | What it does |
|---|---|
create_section | Adds a section (a tab on your docs site) |
update_section | Renames a section, optionally changes its slug |
delete_section | Deletes a section and everything inside |
reorder_sections | Sets the order of all sections |
create_collection | Adds a collection to a section |
update_collection | Renames a collection |
delete_collection | Deletes a collection and everything inside |
move_collection | Moves a collection to a new section, parent, or position |
reorder_collections | Sets the order of collections within a section |
reorder_articles | Sets the order of articles within a collection |
Sections
create_section
Creates a section from a name. The URL slug is derived automatically, and duplicates get a numeric suffix so slugs stay unique.
update_section
Renames a section. By design, renaming does not change the slug, so existing links keep working. The agent can pass a new slug explicitly when you really want the URL to change.
delete_section
Deletes the section and cascades: every collection and article inside is permanently removed, and published articles come off the live site. The response reports exactly how much was deleted.
Section deletion is the most destructive operation in Clayo. If your agent proposes it during a reorganization, make sure the articles you care about have been moved out first.
reorder_sections
Takes the complete ordered list of section ids and applies that order to your site's tab strip. The list must be exhaustive, which prevents a partial reorder from scrambling tabs.
Collections
create_collection
Creates a collection in a section. Pass a parent collection to nest it. Nesting is deliberately capped at one level: collections can contain subcollections, but subcollections cannot contain more collections. Docs stay navigable when the sidebar stays shallow.
update_collection
Renames a collection. Collections have no public URLs, so renaming is always safe for links.
delete_collection
Deletes the collection, its subcollections, and all their articles, permanently. Published articles are removed from the live site.
move_collection
Moves a collection to a different section, nests it under a parent, un-nests it back to the top level, or changes its position among siblings. The one-level nesting rule still applies: a collection that has subcollections cannot itself be nested.
reorder_collections
Sets the order of collections within one section (or within one parent collection). Like section reordering, the id list must be complete.
Articles
reorder_articles
Sets the order of articles within a collection, again with an exhaustive list. To move an article between collections, agents use update_article instead; see Content tools.
Prompts to try
Add an "API reference" section and move the three webhook articles into it.
Reorder the Getting started collection so the install guide comes first.
Merge the "FAQ" collection into "Troubleshooting" and delete the empty one.
