
Overview
When a feature ships, the docs page that explains it goes stale. Fixing it means finding the page, rewriting the section and getting it reviewed before it goes live.
Connect Mintlify through its official MCP server and Agent M edits your pages on a branch, then gives you the link to review it in Mintlify’s editor. On a project with a git repository, the branch opens a pull request you merge to publish.
A Mintlify admin adds api.maintouch.com under MCP > Configure > Redirect URIs for each project you want to connect.
Any member can connect their own Mintlify account from its connector page in Maintouch and pick the projects it covers.
Your connection starts private to you. Turn on sharing to let your teammates’ chats use it too.
Ask for a docs change and Agent M edits the pages on a new branch, then gives you the link to review it.
Agent M publishes or merges only when you ask, and tells you when the change is live.
A custom agent can keep your docs current as part of its instructions and report the branch to review.
Agent M works through your Mintlify account and role, so it only reaches the projects and actions your account can.
An admin has to allow api.maintouch.com as a redirect URI for each project you connect. To publish, Mintlify’s connection to your GitHub, GitLab or Bitbucket repository needs write access.
Only when you ask. Page changes go on a branch by default, and Agent M asks before publishing, merging, deleting pages or changing project settings.
Anything your Mintlify role cannot do. A viewer can only read, and settings like review rules, the git source and custom domains need an admin.
Only if you share it. A new connection is private to you, and you can open it to your org from the Mintlify connector page.