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

Mintlify Base Gives Teams a Wiki That AI Agents Can Edit

Mintlify Base, a beta project type for internal specs and runbooks, can be edited through Slack, Git or an admin MCP, and Pro plans can share pages publicly.

3 min read

MintlifyAI

Isometric 3D illustration of glossy cobalt blue open books on a tiled floor

Mintlify has added Base, a beta project type for internal team knowledge, according to its Oct. 30 changelog. Mintlify describes it as a place for specs, runbooks and onboarding guides that a team and its agents can update.

What Base is

Base is a project type that holds pages and groups only, Mintlify’s documentation says. It has no custom domains, analytics or tabs, unlike a published docs site. Pages are either shared with the whole organization in a Teamspace or kept private to their owner until shared.

How pages get edited

Pages can be changed from the editor, the admin MCP, Slack or Git, per the Oct. 30 changelog. The editor runs in the browser or the desktop app, with the Mintlify agent helping. AI tools such as Claude, ChatGPT and Cursor can read, search and edit a base through the admin MCP. In Slack, the agent answers questions from the base or updates pages on request.

With Git, a team clones the repository and edits MDX files with any tool. Pushed commits update the base. Mintlify can host the repository, or a team can connect GitHub, GitLab, Bitbucket or Azure Repos. Every plan includes the editor, Git sync and the admin MCP.

Plan limits

Starter covers fewer than 1,000 pages, 5 MB file uploads and 100 admin MCP requests a week, and includes 5 seats. Pro allows up to 10,000 pages, 25 MB uploads and 1,000 admin MCP requests per user per week, with 15 seats plus extras. Enterprise allows more than 10,000 pages and adds SSO, SCIM and role-based access control.

Pro and Enterprise admins can share a base page with people outside the organization through a public link. An admin must first turn on “Allow public links,” which is off by default. Viewers need no sign-in and cannot edit. Turning the setting off disables every public link, and re-sharing a page creates a new link.

Each public page has a Markdown version for AI tools. Adding .md to the link returns it, as does a request with an Accept: text/markdown header.

Other changes in the entry

The same changelog entry added GitLab support to Autopilot, plus new mint migrate, mint instructions and mint agent setup commands. It also renamed two admin MCP tools: upload_image is now upload_file, and finalize_image_upload is now finalize_file_upload. Scripts that call the old names need updating.

Key takeaways

  • Base is a beta Mintlify project type for internal specs, runbooks and onboarding guides.
  • Pages can be edited from the editor, the admin MCP, Slack or Git.
  • Pro and Enterprise admins can publish base pages through public links, each with a Markdown version.
  • The admin MCP renamed its image upload tools, which breaks scripts that use the old names.

The take

We think Base is Mintlify’s bet that the same pipeline can serve a team’s internal notes and its public docs. A page that agents can edit is only as reliable as the checks on those edits. Git sync helps, because every change leaves a diff a person can review. We’d start with one low-stakes runbook, read the diffs the agent produces for two weeks, and keep public links off until the team trusts what it writes.