From ab841bfa520560ed24f5cb5f5b496028791cdc30 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Mon, 19 Oct 2026 22:03:28 +0000
Subject: [PATCH] docs: document admin MCP projectType in list_deployments

---
 ai/mintlify-mcp.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/ai/mintlify-mcp.mdx b/ai/mintlify-mcp.mdx
index d96878dd2..270425732 100644
--- a/ai/mintlify-mcp.mdx
+++ b/ai/mintlify-mcp.mdx
@@ -112,6 +112,8 @@ The AI tool acts as you on the deploy branch:
 - **`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.**
 
+Internal projects have no docs site, so they have no publish step. When `list_deployments` returns `projectType: "workspace"`, Mintlify commits edits to the deploy branch automatically, including uploaded images.
+
 Mintlify tracks changes per page. If you and someone else both edited the same page, `publish` publishes the whole page and `discard` reverts the whole page, including the other person's edits.
 
 Mintlify refuses edits to the deploy branch, and changes nothing, when any of the following is true:
@@ -253,7 +255,7 @@ Write tools return the project's updated state under `state`, so the AI tool can
 
 ### Branches and publishing
 
-- **`list_deployments`**: List the projects your connection can access, returning each `{subdomain, name}`. Call this to discover which `subdomain` to pass.
+- **`list_deployments`**: List the projects your connection can access, returning each `{subdomain, name, projectType}`. `projectType` is `site` for a docs site or `workspace` for an internal project. Call this to discover which `subdomain` to pass.
 - **`create_branch`**: Start a new branch off your deploy branch with a `title` that also names its pull request. Returns the `branchName` to pass as `branch`. See [Work on a branch](#work-on-a-branch). You don't need it to [edit the deploy branch directly](#edit-the-deploy-branch-directly).
 - **`list_branches`**: List Git branches available for a project's repository, with optional `query` filtering. Returns the branch names, total count, and the deploy branch. Pass any of them as `branch`.
 - **`status`**: List the edited files, changed `docs.json` keys, and pending navigation diff on `branch`, or on your deploy branch when you omit it. On the deploy branch, lists only your changes.