Integration · Automate and collaborate

Mintlify and Meteor AI agents

Connect Mintlify to an internal Met: search and read your documentation pages, fix a text and reorganize navigation with Mintlify's official MCP.

Book a demo See every integration

How does Mintlify connect to Meteor?

With the Mintlify ready connector, your Met uses Mintlify's admin MCP server with the account the admin authorizes, and it gets 11 tools. It searches a text across every page, reads a full page, walks the navigation and shows a branch's pending changes. It also edits or rewrites pages, creates, renames and moves pages or groups, and changes the site configuration in docs.json. According to Mintlify, what is edited on the deploy branch stays as an unpublished change until someone publishes it, and what is edited on another branch goes through a pull request. Removing a page from the navigation starts turned off.

What it automates

What a Meteor Met does with Mintlify

Fix a detail a customer reported

A customer reports on WhatsApp that a step in your guide no longer works. The Met searches the text across every page, opens the page and applies the targeted fix, which stays pending publication in Mintlify.

Answer with what your documentation says

The Met searches and reads the page that answers the question and replies with that content, without writing anything.

Reorganize the navigation

The Met walks the navigation tree, creates a new group and moves the pages you name into it. If the change leaves the navigation invalid, Mintlify reports it in the response.

Check what changed before publishing

The Met lists a branch's changes against the deploy branch, with who made each one, so your team knows what will go out.

11 tools

Everything your Met can ask Mintlify for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`read`	Returns a page's full MDX on a branch, or on the deploy branch if none is given.
`search`	Finds the lines matching a text or regular expression across every page on a branch.
`list_nodes`	Walks a branch's navigation tree, with filters by parent, type, language, version or tab.
`diff`	Lists every change between a branch and the deploy branch, with its authors and whether they are yours.
`edit_page`	Applies a targeted edit to a page.
`write_page`	Overwrites a page's full MDX content.
`create_node`	Adds a page, group, tab, anchor, version, language, product or dropdown.
`update_node`	Changes a node's properties, such as renaming a group, changing an icon or setting the default version.
`move_node`	Moves a node, including renaming a page's path.
`delete_node`	Removes a node from the navigation. Starts turned off.
`update_config`	Modifies docs.json, with the theme, navigation roots, integrations and SEO settings.

The limits

What the Mintlify integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask you for confirmation in the chat before writing. Removing a page from the navigation starts turned off; the other edits stay on unless the admin turns them off in Connections.
It does not publish when editing. Each edit stays pending on the deploy branch or in a pull request; publishing is a separate server action the admin controls in Connections like the others.
It does not do more than your Mintlify role allows. Changes to protected settings with update_config need an admin role on the project.
It does not replace your team's review. Mintlify recommends reviewing every pull request before merging.
It does not pay your Mintlify plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Mintlify

1

A Mintlify account with access to the project

The OAuth session inherits your account's permissions in the Mintlify dashboard. To change protected settings you need the admin role on the project.
2

Connect it in Met

In Met, open Connections → Mintlify → Connect. A Mintlify window opens so you sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about Mintlify and Meteor

Not right away. According to Mintlify, what is edited on the deploy branch stays as an unpublished change, and what is edited on another branch goes through a pull request. It goes out when someone publishes or merges it.

Removing a node from the navigation starts turned off. If the admin turns it on in Connections, the Met runs it without asking you for confirmation in the chat.

In the Mintlify dashboard, under Settings → Security & access → Connected apps, you revoke the connection's entry. Mintlify invalidates the access within 30 seconds.

You do, with your own Mintlify plan. Meteor does not resell Mintlify: the connector uses your company's account.

Step by step