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

Mintlify's Agent Can Now Reply to and Resolve Doc Comments

Mintlify's Oct. 2 changelog lets its agent answer and close comment threads, adds group-scoped MCP credentials and opens several pull requests per run.

3 min read

MintlifyAI

Isometric 3D illustration of glossy cobalt blue speech bubbles on a tiled floor

Mintlify’s agent can now read open comments and suggestions on a page, reply to threads and resolve them, the company said in its Oct. 2 changelog. The update also tightens access control for the admin MCP server and lets custom automations open more than one pull request per run.

The agent joins the review thread

Mintlify’s agent can now close a comment thread without a person doing it. Beyond reading open comments and suggestions, it replies to threads and resolves them. Editors also get emoji reactions on highlighted text, and the Publish menu now warns about open comments.

Custom automations can now open several pull requests in one run, or add commits to a pull request an earlier run opened. Mintlify also added a Google Docs integration, a read-only personal connection that lets the agent search and read a user’s documents. It is limited to Enterprise plans.

MCP credentials get groups

Group-scoped MCP credentials let an MCP client reach pages restricted to specific user groups. Admins assign groups when they create a credential, and Mintlify said they can’t change a credential’s groups afterward.

The admin MCP server can now edit the deploy branch directly when that branch doesn’t require pull requests. It can also upload images and returns links to private pages, and its diff shows who made each pending change. Custom skills marked public: true now appear to visitors who aren’t signed in on authenticated sites.

Other editor and deploy changes

Deployments now fail if a page’s api, openapi or asyncapi frontmatter is a list instead of a single endpoint string such as “GET /users.” Mintlify said every theme now supports center and frame page modes. In the Maple and Almond themes, center mode keeps the sidebar and centers content beside it.

The editor lets writers click, drag and resize images, including inside frames, cards, tabs and callouts, with handles that work on touch screens. Source mode asks for confirmation on a large change only above 10,000 characters. Admins can switch an existing preview between dashboard login and password protection.

The same entry lists updates to the Mintlify Desktop app, which we covered at its Sept. 24 launch. Those include deep links that open mintlify:// URLs as new tabs, zoom controls, find in page and browser-based sign-in.

Key takeaways

  • Mintlify’s agent can read, reply to and resolve comment threads on a page.
  • MCP client credentials can be scoped to user groups, with groups fixed at creation.
  • The admin MCP server can edit a deploy branch that doesn’t require pull requests.
  • Deployments now fail when api, openapi or asyncapi frontmatter is a list.
  • The Google Docs integration is Enterprise-only.

The take

We think letting the agent resolve threads is the riskiest item in a long list. A resolved thread tells the next reviewer that a person settled the question. Once an agent can resolve it, that signal no longer means what reviewers assume, and Mintlify’s entry doesn’t say whether agent resolutions are labeled or can be reopened. The group-scoped MCP credentials are the more useful change. They let a team give an AI client some private docs without handing it everything. The admin MCP can also write straight to a deploy branch, so we’d turn on branch protection first.