Update to Mintlify MCP

{
  "name": "managing-deployment-settings",
  "description": "Use when changing live deployment settings through the Mintlify Admin MCP — custom domains, authentication, git sources, AI assistant toggle, noindex, custom scripts, source checks, snippets — or when managing org members and roles.",
  "included_files": [],
  "skill_md_contents": "---\nname: managing-deployment-settings\ndescription: Use when changing live deployment settings through the Mintlify Admin MCP — custom domains, authentication, git sources, AI assistant toggle, noindex, custom scripts, source checks, snippets — or when managing org members and roles.\n---\n\n# Managing Deployment Settings\n\n## Overview\n\nDeployment and member operations run through code mode (`execute_code`) with **no checkout and no PR safety net — every write hits the live deployment immediately**. Read current state first, confirm with the user before auth/domain changes, and re-read after writing.\n\n**REQUIRED BACKGROUND:** the `using-code-mode` skill covers return semantics and `{ subdomain }` targeting.\n\n## Namespace `deployment`\n\n| Area | Methods |\n|------|---------|\n| Read state | `get({})` — subdomain, name, basePath, customDomains, noindex, plan, … |\n| Identity | `updateName`, `updateBasePath` ('' or '/docs'), `updateNoindex` |\n| Custom domains | `addCustomDomainV2` (returns DNS records to configure), `removeCustomDomain`, `createCustomHostname`, `getCustomHostnameStatus`, `retriggerCustomHostnameValidation`, `deleteCustomHostname` |\n| Docs auth | `updateAuth` (jwt / oauth-with-client-secret / password / mintlify), `updateUserAuth` (shared-session / jwt / oauth), `toggleAuth`, `deleteAuth`, `deleteUserAuth`, `addAuthPassword`, `deleteAuthPassword`, `deleteAuthJwtKeyPair` |\n| Git sources | `getGitSources`, `addGitSource`, `updateGitSourceItem`, `removeGitSource` (by index), `reorderGitSources`, `setBaseGitSource` |\n| AI assistant | `updateDisableAiChat({ disableAiChat })` — `true` turns the assistant **off**; `updateChatConfig` tunes assistant behavior when it is on |\n| Add-ons | `updateAddOnFeedback`, `updateAddOnRelatedPages`, `updateSearchSettings`, `updatePrivacyConfig`, `updateCustomScripts` |\n| Quality checks | `getSourceChecks`, `updateSourceChecks` (link-rot, spellcheck) |\n| Editor publishing | `updateEditorPublishingSettings` (PR instructions, draft default, merge method) |\n| Snippets | `getSnippets` |\n\nSeveral auth/domain methods require a user-authorized token; `unauthorized` errors mean the token lacks the scope or user grant, not that the method is wrong.\n\n## Namespace `members` (org-scoped)\n\nThese operate on the organization, not a single deployment: `listMembers({ includeRoles? })` (pass `includeRoles: true` to get each member's roles — omitted by default), `updateMemberRoles({ userId, roles })` (SSO-managed roles cannot be changed), `removeMember({ userId })`.\n\n## Example: audit before touching auth\n\n```\nconst current = await deployment.get({});\nconst sources = await deployment.getGitSources({});\n({ current, sources });\n```\n\n## Common mistakes\n\n- Writing without reading — always `deployment.get({})` first and echo the plan to the user for auth, domain, or member removals.\n- Guessing payload shapes — `updateAuth`/`updateUserAuth` are discriminated unions; pull the schema via `search_code_operations` first.\n- Removing git sources by guessed index — list first, indices shift after removal.\n- Renaming preview deployments — `updateName` rejects them.\n- Expecting a rollback path — there is no session/branch here; capture the pre-change state in the same script's logs.\n"
}