Resources · Claude connector

Claude Mintlify connectorWhat Claude can do in your Mintlify account.

The Claude Mintlify connector exposes 15 tools. 5 read your docs and session, 10 write: pages, navigation, configuration, branches and pull requests. Here is how a session works, what Claude can ship, and what can go live without review.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes for a docs team

A product change ships and some pages are suddenly out of date. With this connector, you describe the fix to Claude and it works inside your Mintlify project: it finds the pages, edits them on a dedicated branch, shows you the diff, then opens a pull request. Mintlify adds that every edit buffers on that session branch, so nothing touches your deploy branch before a save.

Fix outdated pages after a release. A parameter was renamed: search finds every line that still uses the old name, edit_page corrects each page, and diff shows the result before anything leaves the branch.

Reorganize a section. The API reference has grown messy: list_nodes walks the navigation tree, create_node adds a new group, and move_node slots pages into it.

Ship it for review. Once the branch looks right, save opens a pull request, or discard_session drops everything if you change your mind.

What Claude cannot promise. Edits sit on a session branch until saved, but depending on your project settings, a save can merge straight away. Claude works with the role your Mintlify account has, so admin-only settings need an admin. And nothing triggers on its own: a new release does not wake Claude up. Scheduled or event-driven jobs belong to automation tools, a separate job you will find from the Integrations hub.

Vocabulary

The vocabulary in one minute

Five words you will meet while connecting Mintlify.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do in that account. Claude picks the tools it needs; the directory sheet lists every one by name.
Authorization
Mintlify's own sign-in screen, where you grant the access Claude will use. Granted once per person, revocable from Mintlify's settings.
Approval
The confirmation Claude waits for before it goes ahead with something that changes your account, shown in the conversation when it matters.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Connect

Connect Mintlify to Claude in three steps

  1. 01

    Find Mintlify

    In Claude, open Customize, then Connectors, and find Mintlify in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector for the organization before members can sign in.

  2. 02

    Sign in to Mintlify

    Click Connect on its row and complete the login in the window Mintlify opens. If the connection ever breaks, use Disconnect, then connect again from the same row.

  3. 03

    Check what you grant

    Read the authorization screen before confirming. It is Mintlify's, not Claude's, and it sets what the access covers. You can revoke it later from your Mintlify dashboard.

Tools

The 15 tools, grouped by what they do

Mintlify gives Claude 15 tools: 5 that read your account, 10 that change something in it.

Two groups: what Claude reads, and what it changes in your project. Tool names stay in English, exactly as Claude shows them.

  • 5 read
  • 10 write

What Claude reads (5)

5 tools

Five tools that look at pages, navigation and the current session without touching them.

read

Fetches the full MDX source of any page on the session branch, from a file path or an identifier. What it returns is the version on the session branch, not the published one.

When it helps
before rewriting the quickstart, you want Claude to go through it line by line.

Sourcemintlify.com · October 1, 2026 ↗

list_nodes

Lists the navigation tree with optional filters. It shows how pages, groups and tabs are arranged, which is the map Claude needs before any restructuring tool runs.

When it helps
you need to see how the guides tab is structured before deciding where a new section belongs.

Sourcemintlify.com · October 1, 2026 ↗

get_session_state

Shows the current branch, the files already edited in this session and the pending navigation diff, a quick status check in the middle of a long job.

When it helps
after a break, you ask Claude where the session stands before carrying on.

Sourcemintlify.com · October 1, 2026 ↗

diff

Lists every difference between the session branch and your deploy branch, so you see exactly what would ship before anything is saved.

When it helps
a reviewer wants the full picture of the session in one place before approving the save.

Sourcemintlify.com · October 1, 2026 ↗

What Claude changes (10)

10 tools

Ten tools that create a branch, edit content or ship it. No source describes a confirmation specific to them, so the general rule below applies.

checkout

Approval: see the rule

Binds the session to a branch of a given project, creating a fresh admin-mcp branch from that project's deploy branch. Calling it again switches which project's session is active.

What Claude asks for
no source documents a confirmation here, so the default approval rule applies.
When it helps
you want a clean branch named after the fix before any edit starts.

Sourcemintlify.com · October 1, 2026 ↗

save

Approval: see the rule

Pushes the session's work to Git, opening a pull request or committing to the session branch. If your project lets the agent push to main and the branch is unprotected, Mintlify merges it at once.

What Claude asks for
nothing specific is documented for this step; it falls under the general rule.
When it helps
the rewrite is done and needs a reviewer.

Sourcemintlify.com · October 1, 2026 ↗

discard_session

Approval: see the rule

Throws away the session and every in-flight edit. Nothing from that session reaches your deploy branch.

What Claude asks for
the sources stay silent on a prompt for this one, so the approvals section's default covers it.
When it helps
a restructuring attempt went the wrong way and you would rather start again from the deploy branch.

Sourcemintlify.com · October 1, 2026 ↗

edit_page

Approval: see the rule

Applies a targeted edit to one page, leaving the rest of its content as it was. The change lands on the session branch.

What Claude asks for
Mintlify's docs describe no confirmation for this tool; Claude's general rule is the reference.
When it helps
one code example uses the old endpoint and only that block must change.

Sourcemintlify.com · October 1, 2026 ↗

write_page

Approval: see the rule

Overwrites a page's full MDX content in one go, rather than patching a passage. The new version sits on the session branch until a save.

What Claude asks for
no source mentions a dedicated prompt; refer to the approvals section.
When it helps
the old troubleshooting page is beyond patching and needs a fresh draft.

Sourcemintlify.com · October 1, 2026 ↗

create_node

Approval: see the rule

Adds a page, group, tab, anchor, version, language, product or dropdown to the navigation. Mintlify warns that invalid nodes can be dropped from the published navigation, so errors get fixed before a save.

What Claude asks for
undocumented for this tool specifically, so it sits under the general approval rule.
When it helps
the billing FAQ needs its own page under the FAQ group.

Sourcemintlify.com · October 1, 2026 ↗

update_node

Approval: see the rule

Modifies a node's properties in place: renaming a group, swapping an icon or setting a default version, without moving anything.

What Claude asks for
the documentation is silent on a prompt; the default rule applies.
When it helps
a group still says Beta although the feature shipped months ago.
Watch out
an invalid navigation comes back as errors to fix before saving.

Sourcemintlify.com · October 1, 2026 ↗

move_node

Approval: see the rule

Moves a node elsewhere in the navigation, including renaming a page's path, which also changes the address readers land on.

What Claude asks for
no tool-level confirmation is described; see the approvals section for what governs it.
When it helps
the webhook pages are scattered and belong together in one group.

Sourcemintlify.com · October 1, 2026 ↗

delete_node

Approval: see the rule

Takes a node out of the navigation. The removal waits on the session branch like any other edit.

What Claude asks for
Mintlify does not document a prompt for removal; the general rule is what you can count on.
When it helps
a retired feature still has a page in the sidebar.
Watch out
invalid nodes may be dropped from the published navigation if left unfixed.

Sourcemintlify.com · October 1, 2026 ↗

update_config

Approval: see the rule

Modifies the project's docs.json: theme, navigation roots, integrations and SEO settings. On protected settings, Mintlify requires an admin role on the project.

What Claude asks for
nothing beyond Claude's default approval behavior is documented here.
When it helps
the brand colors changed and the docs theme must follow.

Sourcemintlify.com · October 1, 2026 ↗

Approvals

What Claude asks before acting

By default, Claude stops and asks before every action it takes on an account for you. On Mintlify, the branch adds a second safety net, unless your project lets saves merge directly.

On Team and Enterprise, workspace owners decide whether members may let some actions through without a prompt, and can limit what any connector may do for the whole organization, keeping reads and closing writes for example. Claude inherits your Mintlify role and nothing more: Mintlify says the OAuth session carries your dashboard permissions. The official per-tool label, read-only versus write and delete, only appears in a connected account's settings.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability. That answer, connector by connector, is not published anywhere.

The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization before members can connect. Your Mintlify role and Git access are separate requirements, set on Mintlify's side. For the current state on your account, check the connector's sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you; nothing starts when code merges or a release goes out.

Only Mintlify documents this connector: Claude's help center has no page for it, so the limits below are the publisher's. Mintlify's page also describes tools that are not on the directory sheet; this page only covers the fifteen listed. The tool list is an observed floor, not a ceiling. The directory badge is not a security audit, and Anthropic writes on every sheet that it does not choose a publisher's tools. For other connectors and automation pages, browse the Integrations hub.

Need help

Need help connecting Mintlify to Claude?

A person reads every message.

FAQ

Questions about the Claude Mintlify connector

01What can Claude do with the Mintlify connector?
Claude can work directly in your Mintlify documentation during a conversation. The fifteen tools on the directory sheet let it start a session on a branch, read and search pages, walk the navigation tree, check the session state and diff, edit or rewrite pages, add, adjust, move or remove navigation nodes, update docs.json, then save the work as a pull request or discard it. Everything happens on a session branch until you save.
02Can Claude publish changes to my live docs?
Yes, in some setups. Saving opens a pull request by default, which a person then reviews. But Mintlify explains that if your project pushes agent changes directly to the deploy branch and that branch has no protection, the pull request merges as soon as Claude saves. Check your agent review setting and branch protection rules before you connect, because that setting decides whether a human sees the edits first. A protected branch keeps a reviewer in the loop.
03Does Claude ask before editing my Mintlify pages?
By default, Claude asks for confirmation before any action it carries out on an account for you. No source describes a confirmation specific to a Mintlify tool, so that default rule covers checkout, edits, navigation changes and save alike. The session branch adds a buffer, since nothing reaches the deploy branch before saving. On Team and Enterprise, owners also decide which actions members may let through without a prompt. You can also read the diff before any save.
04Which Claude plans is the Mintlify connector available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets displays it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner enables a connector before members can connect. Your Mintlify role and Git access are separate requirements. The connector's sheet in the directory shows its current state for your account.
05Does Claude get admin rights on our Mintlify project?
No, it gets yours. Mintlify states that the OAuth session inherits your dashboard permissions, so admin-only actions, such as updating protected settings with update_config, require an admin role on the project. Revoking the grant under Settings, Security & access, Connected apps in your Mintlify dashboard invalidates active session tokens immediately. On Team and Enterprise, a Claude owner can also restrict what the connector may do for everyone. Members cannot lift that limit alone.
06What happens to a session I never saved?
Its branch stays behind. Mintlify explains that a session abandoned without saving or discarding keeps its branch until your next checkout overwrites it. To avoid the clutter, ask Claude to discard the session when a draft goes nowhere, or keep each session focused on one change so the resulting pull request stays easy to review. Revoking the OAuth grant, by contrast, leaves pull requests already opened in place. Close or revert those in your Git provider if needed.
07Claude or an automation tool for Mintlify?
They do different jobs, so choose by use. Claude with this connector edits documentation in conversation: you describe the fix, it finds the pages, shows the diff and opens a pull request. An automation tool reacts to events on a schedule, for example opening a docs task each time an API changes, which this connector never does on its own. For hands-on rewriting and restructuring, Claude fits; for recurring triggers, automation.