Update to Mintlify MCP

{
  "name": "editing-docs-content",
  "description": "Use when changing the text or MDX body of documentation pages through the Mintlify Admin MCP — fixing typos, rewriting sections, updating code samples, or making any content edit that should ship as a commit or PR.",
  "included_files": [],
  "skill_md_contents": "---\nname: editing-docs-content\ndescription: Use when changing the text or MDX body of documentation pages through the Mintlify Admin MCP — fixing typos, rewriting sections, updating code samples, or making any content edit that should ship as a commit or PR.\n---\n\n# Editing Docs Content\n\n## Overview\n\nContent edits happen inside a checked-out editing session on an isolated git branch. Nothing goes live until `save` publishes the branch. Every editor tool fails with \"No active session\" until you `checkout`.\n\n## Workflow\n\n1. `list_deployments` — find the subdomain (skip if pinned or already known).\n2. `checkout { subdomain, slug: \"fix-auth-typos\" }` — opens the session (~7s). Surface the returned `editorUrl` to the user so they can follow along.\n3. Locate content: `search { query }` greps every page on the branch (literal string by default, `regex: true` for regex, results capped at 30KB — refine if `truncated`). `read { path }` returns the full MDX of one page. Both reflect in-session edits immediately.\n4. Edit:\n   - Targeted change → `edit_page { path, oldString, newString, replaceAll? }` (string-replace, like a code editor Edit tool). `replaceAll` is per-page; a docs-wide sweep is one `edit_page` call per matched path from `search`.\n   - Full rewrite → `write_page { path, content }`.\n   - If a search hit might sit in frontmatter rather than body, `read` the page first — frontmatter fixes go through `update_node`, not `edit_page`.\n5. Verify with `diff` (patch per changed file) or `get_session_state` (branch, edited files, nav diff).\n6. `save { title, mode? }` — publishes (~10s).\n\n## Save modes\n\n| mode | Behavior |\n|------|----------|\n| `auto` (default) | Opens a PR; auto-merges only when the deployment's agent review setting is push-to-main and the deploy branch is unprotected (`merged: true` in the response) |\n| `pr` | Opens a PR and always leaves it open for review |\n| `commit` | Commits to the **session branch** in git without opening a PR — a snapshot, never a direct write to the deploy branch |\n\nSaving again in the same session commits to the existing PR branch. `discard_session` abandons everything without publishing.\n\n## Critical: frontmatter is not body content\n\n`edit_page` / `write_page` are for the MDX **body only**. Frontmatter fields (`title`, `sidebarTitle`, `description`, `icon`, `canonical`, `og:*`, `keywords`, `noindex`, `hidden`, …) round-trip through structured node metadata — set them with `update_node { nodeId, data: { type: 'page', ... } }`. The site-level description lives in `docs.json` via `update_config`.\n\n## Common mistakes\n\n- Editing frontmatter with `edit_page` — silently wrong; use `update_node`.\n- Calling `read`/`edit_page` before `checkout` — \"No active session\".\n- Assuming `save` merged: check `merged` in the response; most deployments leave the PR open.\n- Paths are page hrefs (`/quickstart` or `guides/setup`), leading slash and `.mdx` optional.\n- Renaming a page path: `move_node`, never a write to a new path plus delete.\n"
}