What it does
The rule makes Claude Code ask before it runs Mintlify admin MCP tools that publish or merge content (publishing can also merge the pull request), discard changes, delete nodes, rename page paths through moves, or change site-wide settings such as theme, redirects, SEO and integrations. It also covers approving or publishing review requests and project-management writes, including deployment settings, custom domains, Git source, authentication, automations and their pull requests, and members.
It suits teams that let Claude work on Mintlify documentation but want a person to confirm changes that go live or affect the whole site. Page edits, comments and reads still run without a prompt. Edits stay unpublished until publishing, except in projects with auto publish and in bases, where Mintlify commits them to the deploy branch immediately.
Ask rules take precedence over allow rules, so the prompt still appears even if mcp__mintlify-admin is allowed. The rule only covers a server named mintlify-admin, and ask rules for edit_page and write_page must be added separately for auto-publish projects and bases.
Limitations and requirements
Only covers a server named 'mintlify-admin'. In projects with auto publish and in bases, edits reach the deploy branch at once unless ask rules for edit_page and write_page are added. Ask rules override allow rules.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 10
mintlify-mcp-confirm-writes
Ask before Claude runs a Mintlify admin MCP tool that publishes, merges, deletes or has site-wide effect: publish (which can also merge the pull request), discard, delete_node, move_node (renames page paths), update_config (theme, redirects, SEO, integrations), approving or publishing review requests, and every project-management write (deployment settings, custom domain, Git source, authentication, automations and their pull requests, members). Page edits, comments and reads still run freely: they stay unpublished until publish, except in projects with auto publish and in bases, where Mintlif
As shown on www.aitmpl.com when we last read it