Mintlify Index MCP server
Reference for the public Mintlify Index MCP server: connection URL, the context tool, parameters, response format, rate limits, and usage examples.
The Mintlify Index MCP server gives AI tools read-only access to technical documentation and web context. Connect to it at:
https://index.mintlify.comYou do not need to authenticate to the public server. See Connect for Claude Code and Cursor setup instructions.
context tool
Section titled “context tool”Use context to research an implementation task and return compact, source-cited context in one call. The tool is read-only and can access the open web.
-
query(string, required) — Implementation question to research. -
product(string) — Product or company name to use as an additional retrieval hint. -
includeDomains(string[]) — Domains to include in retrieval. When set, retrieval limits results to these domains. -
excludeDomains(string[]) — Domains to exclude from retrieval. -
tokenBudget(integer) — Maximum number of tokens to return. The maximum value is6000. Use the default for focused questions and a larger budget for complex, multi-part tasks.
Output
Section titled “Output”The tool returns Markdown-formatted context assembled from ranked sources. Each section includes a title, source URL, and the relevant source content.
### Configure caching
Source: https://nextjs.org/docs/app/getting-started/caching-and-revalidating
Relevant source content appears here.
--------------------------------The MCP server returns source material for the connected agent to use. The agent decides how to apply that context to your task.
Rate limits
Section titled “Rate limits”Index applies the following per-IP limits to the public MCP server:
| Window | Limit |
|---|---|
| Per second | 10 requests |
| Per day | 5,000 requests |
Requests exceeding either limit return 429 Too Many Requests. Wait before retrying, and use exponential backoff for automated clients.
Protocol behavior
Section titled “Protocol behavior”The Index MCP uses stateless Streamable HTTP:
- Send each JSON Remote Procedure Call (JSON-RPC) request as an HTTP
POST. - Send one JSON-RPC request per HTTP request. Batching is not supported.
- Do not persist or send an MCP session ID between requests.