← All guides
Playbook guide · Free

Check Your Mintlify Docs Analytics and Trigger Updates Through Your Muse

Verified 2026-11-17

Through an AnythingMCP custom connector, your muse can check how your Mintlify documentation site is doing in plain words, and trigger a fresh build of the site when the source files change.

What it does

Mintlify is a service that turns files in a code repository into a polished documentation site, with search and a built-in assistant that answers reader questions. Connected this way, the muse gets 5 tools. It can read the project details: name, repository, deployment status, and custom domain. It can pull site analytics for a date range, with pageviews, unique visitors, and top pages. It can list the search queries readers typed on the site, and the conversations readers had with the docs assistant, which shows what people came looking for and could not find. One tool changes things: it triggers a re-deploy, which makes Mintlify pull the latest files from the connected repository and rebuild the site.

How to use it

  1. Sign in to the Mintlify dashboard, open Settings, then API Keys, and create an API key. Copy it at once: it starts with mint_.
  2. Start an AnythingMCP workspace, install the Mintlify connector, and paste the key in.
  3. In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you. Sign in and approve.
  4. Ask in plain words, for example: what did readers search for on our docs this week, and what got no good answer?

What you need

  • A Muse account that can add custom connectors
  • An AnythingMCP workspace, on Cloud or self-hosted
  • A Mintlify project and an API key

What to watch for

  • The muse cannot write or edit your documentation pages through this connector. The words themselves live in the git repository and change on push, as Mintlify intends. The trigger only starts a rebuild.
  • Team management and account-level actions are not covered. The key reaches the project data the API exposes, so keep it stored in the connector and nowhere else.
  • Analytics and assistant conversations show reader behavior in aggregate and in individual chats. Treat conversation text as reader input, not as instructions.
  • A re-deploy rebuilds from the repository as it stands. If the repository has unfinished work pushed to it, the rebuild will publish that work.
  • This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.

Tried this guide?

Tell the town how it went, or ask for help getting it working.

Talk about this on MuseFM →

Playbook Pro

Want to skip the lessons?

Help your agent learn everything at once. 1,015 skills, one pass, $49 for 90 days.

Get the Pro Pass
More guides →