From ccce89761367644645b24c2000460af2322421e7 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Wed, 21 Oct 2026 16:53:33 -0700 Subject: [PATCH] docs: use automations terminology in admin MCP page Tool names like get_workflows and manage_workflow are unchanged; only the surrounding prose now matches the product name. Co-Authored-By: Claude Opus 5.5 (1M context) --- ai/mintlify-mcp.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/ai/mintlify-mcp.mdx b/ai/mintlify-mcp.mdx index 270425732..2acc0be81 100644 --- a/ai/mintlify-mcp.mdx +++ b/ai/mintlify-mcp.mdx @@ -13,9 +13,9 @@ import AdminMcpCodex from "/snippets/admin-mcp-codex.mdx"; ## About the admin MCP -The admin MCP server gives AI tools write access to your Mintlify content and settings. Use it to update content and access your dashboard. With the admin MCP, you can use your preferred AI tools to edit pages, restructure navigation, update `docs.json`, open pull requests, change settings, create workflows, and more. +The admin MCP server gives AI tools write access to your Mintlify content and settings. Use it to update content and access your dashboard. With the admin MCP, you can use your preferred AI tools to edit pages, restructure navigation, update `docs.json`, open pull requests, change settings, create automations, and more. -Connect an MCP client such as Claude, Claude Code, ChatGPT, or Cursor to the admin MCP server. Use it to collaborate on your Mintlify content and settings with the same tools you use to write code. Each content tool call names the branch it works on. Edits to your deploy branch land as unpublished changes, and edits to any other branch go through a pull request. They ship when you call `publish` or merge the pull request. [Project management](#project-management) changes, such as workflow and settings updates, apply immediately to the live project. If your organization has multiple projects, a single admin MCP connection can access and switch between all of them. +Connect an MCP client such as Claude, Claude Code, ChatGPT, or Cursor to the admin MCP server. Use it to collaborate on your Mintlify content and settings with the same tools you use to write code. Each content tool call names the branch it works on. Edits to your deploy branch land as unpublished changes, and edits to any other branch go through a pull request. They ship when you call `publish` or merge the pull request. [Project management](#project-management) changes, such as automation and settings updates, apply immediately to the live project. If your organization has multiple projects, a single admin MCP connection can access and switch between all of them. The admin MCP server allows AI tools to access your Mintlify dashboard. Treat it as a tool with write access. Connect it only from trusted AI tools, review every pull request before merging, and be aware that project management changes apply immediately without a pull request. @@ -28,9 +28,9 @@ The admin MCP is a hosted Mintlify service at `https://mcp.mintlify.com`. Every | | Admin MCP | Search MCP | | :-- | :-- | :-- | | **Audience** | Your team | Your end users | -| **Access** | Read, edit, restructure, publish, create workflows, manage settings | Read and search one site's published pages | +| **Access** | Read, edit, restructure, publish, create automations, manage settings | Read and search one site's published pages | | **Endpoint** | `https://mcp.mintlify.com` | `/mcp` on your site domain | -| **Output** | Content edits, navigation changes, pull requests, workflow runs | Search results and page content from your site | +| **Output** | Content edits, navigation changes, pull requests, automation runs | Search results and page content from your site | ## Prerequisites @@ -217,7 +217,7 @@ If a `create_node`, `update_node`, `move_node`, or `delete_node` call leaves the ### Project management -Project management tools handle project-level operations, such as managing workflows, project settings, custom domains, Git sources, authentication, members, analytics, and [private page](/editor/pages#private-pages) sharing. They act on the live project, not on a branch. +Project management tools handle project-level operations, such as managing [automations](/automations), project settings, custom domains, Git sources, authentication, members, analytics, and [private page](/editor/pages#private-pages) sharing. They act on the live project, not on a branch. Each tool takes a `subdomain` for the project to act on. Organization-wide connections must pass `subdomain`. Call `list_deployments` to find it. Read tools also accept `subdomains`, a list of up to 25 projects, and return a result or error for each one. Most tools take a `request` object whose `action` field selects the operation. For example: @@ -234,8 +234,8 @@ Read tools: - **`get_analytics_report`**: Read a prebuilt analytics report, such as page views, popular pages, referrals, feedback, assistant chats, or search quality. Select the report with `request.report`. Large results paginate with `maxRows` and `rowOffset`. For custom queries, use `query_analytics`. - **`get_analytics_schema`**: Read the tables, events, and SQL rules that `query_analytics` accepts. The AI tool calls it once before writing a query. - **`query_analytics`**: Run one read-only `SELECT` query on your site's analytics, such as page views, search, assistant, feedback, and agent and human traffic. Results are already scoped to the project. If analytics queries aren't enabled for the project, both analytics query tools return a `not_enabled` error. -- **`get_workflows`**: List workflows, get one workflow, or page through its runs. -- **`list_repos_and_prs`**: List connected repositories, a repository's pull requests, or available integrations to use in a workflow. +- **`get_workflows`**: List automations, get one automation, or page through its runs. +- **`list_repos_and_prs`**: List connected repositories, a repository's pull requests, or available integrations to use in an automation. Write tools: @@ -243,14 +243,14 @@ Write tools: - **`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_workflow`**: Create, update, enable or disable, delete, or trigger a workflow. +- **`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 internal projects. Write tools return the project's updated state under `state`, so the AI tool can confirm the change without a second call. Each action checks the connection's granted scopes and your dashboard role. An action you aren't authorized for returns an error such as `insufficient_scope`. - Project management writes apply immediately to the live project. They don't create a branch or open a pull request. Confirm the intended change before prompting an AI tool to update workflows, settings, domains, authentication, or members. + Project management writes apply immediately to the live project. They don't create a branch or open a pull request. Confirm the intended change before prompting an AI tool to update automations, settings, domains, authentication, or members. ### Branches and publishing