docs: note that switching auth types only carries over JWT

ai/mintlify-mcp.mdx

@@ -123,7 +123,7 @@
 
 The AI tool acts as you on the deploy branch:
 
 - **Edits are live to collaborators.** Anyone else editing the deploy branch in the dashboard sees the AI's changes as they happen.
 - **`publish` publishes only your changes.** It commits your pending changes straight to the deploy branch, like clicking **Publish** in the editor. Other people's unpublished changes stay pending. Your own unpublished edits from the dashboard editor publish too.
 - **`discard` reverts only your changes.** It returns `discardedChanges` with the number of changes it reverted. Other people's changes and the branch itself stay untouched.
 - **`status` lists only your changes.**
@@ -136,10 +136,10 @@
 
 - **Push directly to your deploy branch** is off in your [publishing settings](#publishing).
 - Branch protection on your deploy branch requires pull requests, or Mintlify can't check your branch protection rules.
 - Editing the deploy branch is locked in the dashboard editor.
 - You connected with a client or machine-to-machine token instead of an OAuth login. These tokens aren't tied to a user, so they have no "own" changes.
 
 Mintlify checks these conditions on every edit and caches your branch protection rules for up to 30 seconds. Comment tools still work on the deploy branch when edits to it are refused. If your deploy branch starts requiring a pull request after you edit it, `publish` returns `branch_protected` and your changes stay pending. Open the dashboard editor to move them to a new branch.
 
 ### Projects with auto publish
 
@@ -147,7 +147,7 @@
 
 Mintlify refuses `create_branch` and calls on any other branch in these projects, and changes nothing. If your connection covers only that project, the admin MCP doesn't list `create_branch` or `list_branches`.
 
 **Push directly to your deploy branch** and branch protection don't block deploy branch edits in a project with auto publish. Mintlify still refuses edits when editing the deploy branch is locked in the dashboard editor, or when you connected with a client or machine-to-machine token.
 
 ## Work on a branch
 
@@ -167,7 +167,7 @@
 
 This toggle shares the same `agentReviewProcess` setting as the Slack and dashboard agent, so any change here also applies to those flows.
 
 The toggle is disabled in three cases:
 
 - **Your deploy branch requires a pull request.** If branch protection rules or required approvals prevent direct pushes, MCP changes always go through a pull request regardless of this setting.
 - **Mintlify hosts your project.** For Mintlify-hosted sites, MCP changes always push directly, unless branch protection still requires a pull request.
@@ -280,7 +280,7 @@
 - **`update_deployment_settings`**: Change one dashboard setting, such as `noindex`, `base_path`, `name`, `disable_ai_chat`, `search_settings`, `privacy`, `custom_scripts`, or an add-on. Use `update_config` for `docs.json` settings.
 - **`manage_custom_domain`**: Add or remove a custom domain, provision its hostname, or retrigger hostname validation.
 - **`manage_git_source`**: Add, update, remove, or reorder the Git repositories a project builds from, or set the base source.
-- **`manage_access_auth`**: Configure or remove site [authentication](/deploy/authentication-setup), add or delete passwords, configure end-user authentication, or switch which one is active.
+- **`manage_access_auth`**: Configure or remove site [authentication](/deploy/authentication-setup), add or delete passwords, configure end-user authentication, or switch which one is active. Switching carries over only a JWT configuration. If the active configuration uses any other type, the switch fails with a `409` error and leaves your site unchanged. To change to a different type, configure the new authentication directly.
 - **`manage_workflow`**: Create, update, enable or disable, delete, or trigger an automation.
 - **`manage_workflow_prs`**: Merge or close a pull request that an [automation](/automations) run opened. To merge a pull request for a branch the AI tool edited, use `publish` with `merge: true` instead.
 - **`manage_members_sharing`**: List or remove organization members, update their roles, or manage private page grants and moves in bases.