Skip to content
The Docs Report
Tuesday, November 17, 2026NewsletterRSS

Mintlify's CLI Now Lets Coding Agents Deploy a Site Before Sign-Up

Mintlify's Oct. 30 changelog lets a coding agent run mint deploy before the user has an account, then hand the site over with mint claim.

2 min read

MintlifyAI

Product photo of a white rocket on a cobalt blue, teal and violet gradient

A coding agent can now create and deploy a Mintlify site before its user has an account, according to Mintlify’s Oct. 30 changelog. The agent runs mint deploy, and the user later takes ownership of the site with mint claim.

Agents can deploy first and sign up later

The changelog says an agent can run mint deploy “before you have an account,” including on every push from GitHub Actions. The user claims the site afterward with mint claim. Mintlify’s agent instructions add that the user completes OAuth sign-in as part of setup.

One command wires up the agent

mint agent setup installs Mintlify skills and connects the admin MCP for Claude Code, Codex or Cursor in one step, per the entry. A second command, mint instructions, lets a coding agent look up how to do common tasks, such as publishing a new site or adding a custom domain.

Migration can go to an agent

mint migrate prints step-by-step instructions for moving content to Mintlify from 21 sources. Passing --agent has Claude Code, Codex, Cursor or Gemini carry out the migration instead.

Validation catches pages that build but break

mint validate now checks for content that builds but doesn’t render correctly. It lists each finding with its file, line and rule. The entry adds --fix to repair common issues, --enable and --disable to choose rules, and --format json for a machine-readable report.

Admin MCP changes

The same entry gave the admin MCP a read_page_history tool that lists a page’s saved versions, a read_inbox tool for comments, mentions and suggested edits, and a read_skill tool. The header x-mintlify-toolset: knowledge limits a connection to search and read tools. Two upload tools were renamed: upload_image is now upload_file, and finalize_image_upload is now finalize_file_upload. Prompts and scripts that call the old names need updating.

Key takeaways

  • mint deploy works before the user has an account, and mint claim transfers the site.
  • mint agent setup connects Claude Code, Codex or Cursor to the admin MCP in one command.
  • mint validate flags pages that build but render wrongly, and can fix some of them.
  • The renamed admin MCP upload tools break scripts that use the old names.

The take

We think the notable change is who starts the project. The agent can go first, and a person inherits a site that already exists. A site can then be live before anyone has settled who owns it. Our read is that an unclaimed site is a new deployment and needs an owner like any other. Before pointing a GitHub Action at mint deploy, we’d name who will run mint claim. We’d also search CI scripts for the old upload tool names.