Rank #2 of 5 in Developer Docs Platforms
Install
npm i -g mintShowcase


Try itExperimental
See what an agent can do with Mintlify before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si -X POST https://mcp.mintlify.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai docs — stories about ai docs in this arenaAi docsevidence →
Stories about ai docs in this arena
Analytics insights — stories about analytics insights in this arenaAnalytics insightsevidence →
Stories about analytics insights in this arena
Api reference — stories about api reference in this arenaApi referenceevidence →
Stories about api reference in this arena
Authoring editing — stories about authoring editing in this arenaAuthoring editingevidence →
Stories about authoring editing in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Collaboration review — stories about collaboration review in this arenaCollaboration reviewevidence →
Stories about collaboration review in this arena
Customization — bending the product to your needs — settings, theming, extension pointsCustomizationevidence →
Bending the product to your needs — settings, theming, extension points
Docs as code — stories about docs as code in this arenaDocs as codeevidence →
Stories about docs as code in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Publishing hosting — stories about publishing hosting in this arenaPublishing hostingevidence →
Stories about publishing hosting in this arena
Search discovery — stories about search discovery in this arenaSearch discoveryevidence →
Stories about search discovery in this arena
Versioning localization — stories about versioning localization in this arenaVersioning localizationevidence →
Stories about versioning localization in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 0 paid · 1 enterprise · 38 not stated in evidence
Follow the green: where the map greys out is where Mintlify stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~7/10
unlocks → Webhooks · Official SDKs · Scoped API keys · Versioning policy
Subscribe to events via webhooks
—–
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
!4/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
~5/10
unlocks → Official SDKs
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~6/10
Explore an interactive API reference with runnable examples
✓8/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓8/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~6/10
Set up automations that run autonomously in the background
✓8/10
Ai docs — stories about ai docs in this arenaAi docs
Stories about ai docs in this arena
My published docs site exposes its own MCP server that my users' agents can query for search and page content
✓8/10
Agent output
An embedded AI assistant on my docs site answers reader questions with citations into my content
✓9/10
A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests
✓9/10
Analytics insights — stories about analytics insights in this arenaAnalytics insights
Stories about analytics insights in this arena
Api reference — stories about api reference in this arenaApi reference
Stories about api reference in this arena
Authoring editing — stories about authoring editing in this arenaAuthoring editing
Stories about authoring editing in this arena
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Collaboration review — stories about collaboration review in this arenaCollaboration review
Stories about collaboration review in this arena
Customization — bending the product to your needs — settings, theming, extension pointsCustomization
Bending the product to your needs — settings, theming, extension points
Docs as code — stories about docs as code in this arenaDocs as code
Stories about docs as code in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Publishing hosting — stories about publishing hosting in this arenaPublishing hosting
Stories about publishing hosting in this arena
Search discovery — stories about search discovery in this arenaSearch discovery
Stories about search discovery in this arena
Versioning localization — stories about versioning localization in this arenaVersioning localization
Stories about versioning localization in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 7/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | disputed | 4/10 | Dcontradicted | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 6/10 | Cclaimed | |
My published docs site automatically serves llms.txt (and a full-content variant) so agents can index it C Agent output | ai-native user | Ai docs — stories about ai docs in this arenaAi docs | 3 | full | 9/10 | Tprobed | |
Every published page serves clean markdown at its URL (e.g. appending .md) so agents skip the HTML C Agent output | ai-native user | Ai docs — stories about ai docs in this arenaAi docs | 3 | full | 8/10 | Tprobed | |
My API reference pages are generated from an OpenAPI spec and stay in sync when the spec changes C Spec driven | developer | Api reference — stories about api reference in this arenaApi reference | 3 | full | 8/10 | Cclaimed | |
My docs live in my own git repository — branches, pull requests, and merges drive what gets published C Git workflow | developer | Docs as code — stories about docs as code in this arenaDocs as code | 3 | full | 8/10 | Cclaimed | |
My published docs site exposes its own MCP server that my users' agents can query for search and page content C Agent access | ai-native user | Ai docs — stories about ai docs in this arenaAi docs | 3 | full | 8/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Cclaimed | |
Readers get fast, typo-tolerant, relevance-ranked search over the whole docs site out of the box C Search | developer | Search discovery — stories about search discovery in this arenaSearch discovery | 3 | partial | 6/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 5/10 | Xcommunity | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | disputedenterprise | 5/10 | Dcontradicted | |
I publish versioned documentation per product or API version, and readers switch versions from the site C Versioning | developer | Versioning localization — stories about versioning localization in this arenaVersioning localization | 3 | partial | 3/10 | Cclaimed | |
I author pages in Markdown/MDX with rich components — tabs, callouts, code groups, steps — without writing custom HTML C Authoring | technical writer | Authoring editing — stories about authoring editing in this arenaAuthoring editing | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests C Writer agent | ai-native user | Ai docs — stories about ai docs in this arenaAi docs | 2 | full | 9/10 | Cclaimed | |
An embedded AI assistant on my docs site answers reader questions with citations into my content C Assistant | ai-native user | Ai docs — stories about ai docs in this arenaAi docs | 2 | full | 9/10 | Cclaimed | |
I serve docs on my own custom domain or as a /docs subpath of my main site C Domains | devrel lead | Publishing hosting — stories about publishing hosting in this arenaPublishing hosting | 2 | full | 9/10 | Cclaimed | |
Every docs pull request gets a shareable preview deployment before it merges C Git workflow | developer | Docs as code — stories about docs as code in this arenaDocs as code | 2 | full | 8/10 | Cclaimed | |
I see page views, search terms, and reader feedback so I know which docs work and which fail C Analytics | devrel lead | Analytics insights — stories about analytics insights in this arenaAnalytics insights | 2 | full | 8/10 | Cclaimed | |
Non-technical teammates can edit docs in a visual web editor without touching git, and their changes flow into the same source of truth C Authoring | technical writer | Authoring editing — stories about authoring editing in this arenaAuthoring editing | 2 | full | 8/10 | Cclaimed | |
Readers can try real API calls from an interactive playground embedded in the reference docs C Playground | developer | Api reference — stories about api reference in this arenaApi reference | 2 | full | 8/10 | Cclaimed | |
Teammates propose changes that go through review — comments, approvals, and a merge step — before they publish C Review | technical writer | Collaboration review — stories about collaboration review in this arenaCollaboration review | 2 | full | 8/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
I customize themes, fonts, and layout — down to custom CSS/JS or my own components — so the docs match my brand C Theming | devrel lead | Customization — bending the product to your needs — settings, theming, extension pointsCustomization | 2 | partial | 5/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
CI validation catches broken links and invalid configuration before the site publishes C Quality gates | developer | Docs as code — stories about docs as code in this arenaDocs as code | 2 | partial | 4/10 | Cclaimed | |
Export my entire docs site as a static bundle and host it anywhere, so my content is never locked in C Portability | developer | Publishing hosting — stories about publishing hosting in this arenaPublishing hosting | 2 | partial | 4/10 | Xcommunity | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
My docs analytics distinguish AI-agent traffic from human traffic so I can see who — or what — is actually reading C Analytics | ai-native user | Analytics insights — stories about analytics insights in this arenaAnalytics insights | 2 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Automated checks lint my content against a style guide and flag issues before they publish C Quality | technical writer | Authoring editing — stories about authoring editing in this arenaAuthoring editing | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 6/10 | Cclaimed | |
I gate some or all docs behind authentication — password, JWT, or SSO — for customers-only content G Access control | devrel lead | Publishing hosting — stories about publishing hosting in this arenaPublishing hosting | 1 | partial | 5/10 | Cclaimed | |
I publish my docs in multiple languages with translated navigation and content C Localization | technical writer | Versioning localization — stories about versioning localization in this arenaVersioning localization | 1 | none | untested | none yet | |
Reusable snippets and variables keep repeated content in sync across pages C Content reuse | technical writer | Authoring editing — stories about authoring editing in this arenaAuthoring editing | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 31 stories with headroom
What would move Mintlify’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
All MCP-related evidence describes Mintlify exposing its own MCP servers (search, admin, index) for external AI tools like Claude/Cursor/ChatGPT to consume — the opposite direction of this story.
Authoring editing — stories about authoring editing in this arenaI author pages in Markdown/MDX with rich components — tabs, callouts, code groups, steps — without writing custom HTML
nonemoves PA Scoreimpact 30
Missing: any documentation of MDX component library, callout/tab/code-group syntax examples, or component authoring guides.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: any documented privacy policy, opt-out mechanism, or contractual terms about AI training data use.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Mintlify documents a REST API (mintlify-docs-21) and CLI, but there is no evidence of official client SDKs (e.g., Python/JS/Go libraries) for developers to build against, and probes for an OpenAPI spec for Mintlify's own API returned 404s (mintlify-probe-3), suggesting no such SDK tooling exists.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
No evidence of webhook subscription capability; Mintlify offers automations triggered by repo pushes/integration events and a REST API to trigger deployments, but nothing about outbound webhooks for subscribing to events.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
The evidence pack contains extensive documentation on Mintlify's own API (REST API for deployments, MCP servers, CLI, etc.) but no mention of API versioning schemes or a documented deprecation policy for Mintlify's own APIs/products.
Versioning localization — stories about versioning localization in this arenaI publish versioned documentation per product or API version, and readers switch versions from the site
partialq3/10moves PA Scoreimpact 21
Missing: explicit docs on defining/publishing multiple versions, a reader-facing version switcher, and any hands-on confirmation that this works as described.
Analytics insights — stories about analytics insights in this arenaMy docs analytics distinguish AI-agent traffic from human traffic so I can see who — or what — is actually reading
nonemoves PA Scoreimpact 20
Mintlify's analytics docs describe traffic, assistant conversations, search queries, engagement, and reader feedback metrics, but none of the evidence mentions segmenting or distinguishing AI-agent/bot traffic from human readers.
Showing the top 8 of 31 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map8 surfaces · 39 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs38 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Test against a sandbox environment without touching production data
- My published docs site exposes its own MCP server that my users' agents can query for search and page content
- My published docs site automatically serves llms.txt (and a full-content variant) so agents can index it
- Every published page serves clean markdown at its URL (e.g. appending .md) so agents skip the HTML
- An embedded AI assistant on my docs site answers reader questions with citations into my content
- A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests
- I see page views, search terms, and reader feedback so I know which docs work and which fail
- Readers can try real API calls from an interactive playground embedded in the reference docs
- My API reference pages are generated from an OpenAPI spec and stay in sync when the spec changes
- Non-technical teammates can edit docs in a visual web editor without touching git, and their changes flow into the same source of truth
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Teammates propose changes that go through review — comments, approvals, and a merge step — before they publish
- I customize themes, fonts, and layout — down to custom CSS/JS or my own components — so the docs match my brand
- My docs live in my own git repository — branches, pull requests, and merges drive what gets published
- Every docs pull request gets a shareable preview deployment before it merges
- CI validation catches broken links and invalid configuration before the site publishes
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Self-host the core product
- I serve docs on my own custom domain or as a /docs subpath of my main site
- Export my entire docs site as a static bundle and host it anywhere, so my content is never locked in
- Readers get fast, typo-tolerant, relevance-ranked search over the whole docs site out of the box
- I publish versioned documentation per product or API version, and readers switch versions from the site
Pricing docs8 stories
- Get AI-generated insights and suggestions from my data inside the product
- My published docs site exposes its own MCP server that my users' agents can query for search and page content
- I see page views, search terms, and reader feedback so I know which docs work and which fail
- Readers can try real API calls from an interactive playground embedded in the reference docs
- Non-technical teammates can edit docs in a visual web editor without touching git, and their changes flow into the same source of truth
- Version, review, and roll back my automations
- I gate some or all docs behind authentication — password, JWT, or SSO — for customers-only content
- I serve docs on my own custom domain or as a /docs subpath of my main site
Blog docs6 stories
- Set up automations that run autonomously in the background
- My published docs site automatically serves llms.txt (and a full-content variant) so agents can index it
- A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
Use cases docs5 stories
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests
- Readers can try real API calls from an interactive playground embedded in the reference docs
- My API reference pages are generated from an OpenAPI spec and stay in sync when the spec changes
Hacker News4 stories
llms.txt3 stories
OpenAPI spec3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si -X POST https://mcp.mintlify.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -si -X POST https://mcp.mintlify.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401
access-control-allow-origin: *
cache-control: public, max-age=0, must-revalidate
cf-cache-status: DYNAMIC
cf-ray: a38073806b14c07b-IAD
content-type: application/json; charset=utf-8
date: Tue, 08 Sep 2026 19:45:01 GMT
etag: W/"55-ne2eiByQyrEieB2qeY4xI2hKdhQ"
link: <https://www.mintlify.com/index.md>; rel="alternate"; type="text/markdown"
server: Vercel
set-cookie: AWSALB=enaxelPP9AGMWm7C3OMs315JW5NZv5SAXqLE1cwG9XyorBwBNkdvmZmXSo3Z8JislcSnrZdNXQKaFABhlwjFVyQRZ7U86BwKMLFMhBTBw9pwXwZkHpLtm5kUbxs1; Expires=Tue, 15 Sep 2026 19:45:01 GMT; Path=/
set-cookie: AWSALBCORS=enaxelPP9AGMWm7C3OMs315JW5NZv5SAXqLE1cwG9XyorBwBNkdvmZmXSo3Z8JislcSnrZdNXQKaFABhlwjFVyQRZ7U86BwKMLFMhBTBw9pwXwZkHpLtm5kUbxs1; Expires=Tue, 15 Sep 2026 19:45:01 GMT; Path=/; SameSite=None; Secure
set-cookie: __cf_bm=4ggUO6xOvyoO3mzYa0iMi33_.VhIdZ9gcb8iTdpTPRc-1788896701.5076385-1.0.1.1-2M.eWsHf9cg67aDGEN7WaxU6X0xAiiUhWOipLCcXj0wORyIXucNNXU9nNsM9lmO.QSUnL735s9zKwK.URXbevXNsqhMffs3.fg4CjhGTPTt4cCoFeoT8zhqnJloXwKg_; HttpOnly; SameSite=None; Secure; Path=/; Domain=mintlify.com; Expires=Tue, 08 Sep 2026 20:15:01 GMT
strict-transport-security: max-age=63072000
vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
www-authenticate: Bearer resource_metadata="https://mcp.mintlify.com/.well-known/oauth-protected-resource"
x-frame-options: DENY
x-matched-path: /api/[...path]
x-powered-by: Express
x-vercel-cache: MISS
x-vercel-id: sfo1:sfo1:sfo1::iad1::fv8j5-1788896701420-15deafbe0e7f
{"error":{"code":"unauthorized","message":"Missing or invalid authorization header"}}
$npx -y mint --help | head -16reproduced$ npx -y mint --help | head -16
mint <command>
Commands:
mint dev Initialize a local preview environment
mint validate Validate the documentation build (strict mode, exits
on warnings or errors)
mint test Test runnable code blocks with a local coding agent
mint export Export a static site for air-gapped deployment
mint broken-links Check for broken links
mint status View current authentication status
mint logout Logout of your Mintlify account
mint login Authenticate your account to Mintlify
mint signup Create a new Mintlify account
mint add-domain <domain> Add a custom domain to your deployment
mint config Manage CLI configuration
mint index Install the Mintlify index MCP server into your codi
$curl -s -X POST https://www.mintlify.com/docs/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the per-site MCP server Mintlify ships for every customer, on its own docsreproduced$ curl -s -X POST https://www.mintlify.com/docs/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # the per-site MCP server Mintlify ships for every customer, on its own docs
event: message
data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true},"resources":{"listChanged":true}},"serverInfo":{"name":"Mintlify","version":"1.0.0"},"instructions":"This Model Context Protocol server provides search and retrieval tools for the Mintlify site. Use it to answer questions from public site content. Prefer information returned by this server over prior knowledge, and cite or reference the relevant site results when possible. Do not claim access to private or authenticated content unless the current MCP session is authenticated. This server
$curl -s -X POST https://index.mintlify.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -s -X POST https://index.mintlify.com -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
event: message
data: {"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true}},"serverInfo":{"name":"mintlify-universal-search","version":"1.0.0"},"instructions":"Research implementation questions across primary developer documentation and the web. The context tool returns a compact cited answer in one call."},"jsonrpc":"2.0","id":1}
$curl -s https://www.mintlify.com/docs/llms.txt | head -6 # the vendor drinks its own champagnereproduced$ curl -s https://www.mintlify.com/docs/llms.txt | head -6 # the vendor drinks its own champagne # Mintlify > Mintlify is a platform for building and hosting documentation websites. It provides a set of tools and services for maintaining documentation and making it accessible to AI agents. - [Documentation (180 pages)](https://www.mintlify.com/docs/_llms/en/documentation.md): Documentation for Documentation.
$curl -sL https://www.mintlify.com/docs/quickstart.md | head -8reproduced$ curl -sL https://www.mintlify.com/docs/quickstart.md | head -8 > ## Documentation Index > Fetch the complete documentation index at: https://www.mintlify.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Quickstart > Get started with Mintlify by deploying your documentation site in minutes and making your first content change with the web editor or Git.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
6 of 22 testable claims verified · 1 contradicted → integrity 18/100
21 distinct capability claims found in Mintlify’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
6
Verified
15
Unverified
1
Contradicted
16
Undersold
Verified (7)
“Automatically generate llms.txt and llms-full.txt so AI tools can index the docs”
My published docs site automatically serves llms.txt (and a full-content variant) so agents can index itfullproof ↗
“AI tools can be given write access via MCP to edit pages, update settings, and open PRs against docs content”
“Every page serves a clean Markdown version by appending .md to its URL”
Every published page serves clean markdown at its URL (e.g. appending .md) so agents skip the HTMLfullproof ↗
“A skill.md file is hosted at the project root describing product capabilities for AI agents”
Point an agent at llms.txt or agent-oriented docsfullproof ↗
“An official CLI lets you preview docs locally, test changes live, and catch build errors before deploy”
“A REST API lets you trigger deployments, embed the assistant, export analytics, and manage docs programmatically”
Drive the product through a documented public APIpartialproof ↗
“A separate Index MCP server gives AI tools read-only access to technical documentation and web context”
Unverified (15)
“Deploy a docs site quickly and make edits via either the web editor or a Git-based workflow”
My docs live in my own git repository — branches, pull requests, and merges drive what gets publishedfullproof ↗
“Deploy a docs site quickly and make edits via either the web editor or a Git-based workflow”
Non-technical teammates can edit docs in a visual web editor without touching git, and their changes flow into the same source of truthfullproof ↗
“Embed an AI chat assistant on the docs site that answers questions, cites sources, and generates code examples”
An embedded AI assistant on my docs site answers reader questions with citations into my contentfullproof ↗
“A platform agent researches, plans, and writes documentation, opening PRs with proposed changes for review”
A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requestsfullproof ↗
“Automate doc maintenance by running the agent on a schedule, on repo pushes, or on integration events”
“Automate doc maintenance by running the agent on a schedule, on repo pushes, or on integration events”
Set up automations that run autonomously in the backgroundfullproof ↗
“Site exposes a hosted search MCP server that lets AI tools like Claude/Cursor/ChatGPT search and retrieve content”
My published docs site exposes its own MCP server that my users' agents can query for search and page contentfullproof ↗
“The web editor includes a built-in AI agent that writes/edits content, leaves comments, searches the site, and configures settings”
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
“API reference pages are generated automatically from OpenAPI spec files, including endpoints and navigation”
My API reference pages are generated from an OpenAPI spec and stay in sync when the spec changesfullproof ↗
“Host docs on your own custom domain, subdomain, or subpath with managed DNS/TLS”
I serve docs on my own custom domain or as a /docs subpath of my main sitefullproof ↗
“A central docs.json file configures branding, navigation, integrations, and API settings for the site”
I customize themes, fonts, and layout — down to custom CSS/JS or my own components — so the docs match my brandpartialproof ↗
“Each pull request gets a unique preview URL so reviewers can see doc changes live before merging”
Every docs pull request gets a shareable preview deployment before it mergesfullproof ↗
“Analytics dashboard tracks traffic, assistant conversations, search queries, engagement, and feedback”
I see page views, search terms, and reader feedback so I know which docs work and which failfullproof ↗
“In-product search can be tuned with ranking boosts, max results per query, and product/version filters”
Readers get fast, typo-tolerant, relevance-ranked search over the whole docs site out of the boxpartialproof ↗
“Editor supports previewing, sharing, approving, and merging pull requests without leaving the tool”
Teammates propose changes that go through review — comments, approvals, and a merge step — before they publishfullproof ↗
Contradicted (1)
“Run Mintlify in your own cloud or on-prem environment, on AWS or any Kubernetes platform”
Undersold (16)
Run the product headlessly / in CI for automationpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Operate the product with natural-language commandsfullproof ↗
Explore an interactive API reference with runnable examplesfullproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)partialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Readers can try real API calls from an interactive playground embedded in the reference docsfullproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
CI validation catches broken links and invalid configuration before the site publishespartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
I gate some or all docs behind authentication — password, JWT, or SSO — for customers-only contentpartialproof ↗
Export my entire docs site as a static bundle and host it anywhere, so my content is never locked inpartialproof ↗
I publish versioned documentation per product or API version, and readers switch versions from the sitepartialproof ↗
Business model
Starter plan is free; Pro is ~$450/month with 5 editor seats and 10,000 AI credits/month ($0.01 per credit overage); Enterprise is custom.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime MCP up · llms.txt up (tracking since Sep 10 '26)
