[mintlify]

Documents that the admin MCP edit_page tool now accepts an edits list, so an AI tool can apply up to 100 replacements to a page in one call.

Previously edit_page took one oldString/newString pair per call. The new list applies each replacement in order, and the whole batch fails together if any edit fails.

Also documents the new notRendered field on write_page and edit_page responses, which lists markup the Mintlify editor drops (scripts, style blocks, event handlers, JavaScript expressions) with the line, the reason and a suggested alternative. edit_page only reports markup the edit adds.

Based on two merged admin MCP changes: "apply several edit_page replacements in one call" and "report MDX the editor drops from write_page and edit_page".

Duplicate check: searched open and recent docs PRs by hunterchen7 and ethanpalm, mintlify[bot] PRs, and titles containing "MCP" and "edit_page"; none cover this.

---

Note

Low Risk
Documentation-only changes to the admin MCP reference with no runtime or security impact.

Overview
Updates the admin MCP docs for edit_page and write_page to match new API behavior.

edit_page can still take a single oldString/newString pair, or an edits list (up to 100 replacements) applied in order on the previous result, with all-or-nothing semantics if any replacement fails. The doc also notes that responses can include notRendered for unsafe markup introduced by the edit (not markup already on the page).

write_page now documents the same notRendered response shape when full-page MDX includes elements the Mintlify editor strips (e.g. <script>, <style>, event handlers), including per-item element, line, why, and suggested instead alternatives.

^{Reviewed by Cursor Bugbot for commit e9cf242. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Mintlify Docs	🟢 Ready	View Preview	Oct 22, 2026, 6:07 PM