Mintlify Docs

{
  "mcpServers": {
    "com.mintlify/searchmcp": {
      "url": "https://www.mintlify.com/docs/mcp"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

3 shown · authentication unknown

• Query documentation filesystem

  query_docs_filesystem_mintlify

  Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Mintlify documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything - `cat /openapi/zh/analytics.openapi.json | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted at: `/openapi/zh/analytics.openapi.json`, `/openapi/fr/analytics.openapi.json`, `/openapi/es/analytics.openapi.json`, `/openapi/analytics.openapi.json`, `/openapi/zh/admin-openapi.json`, `/openapi/fr/admin-openapi.json`, `/openapi/es/admin-openapi.json`, `/openapi/admin-openapi.json`, `/openapi/zh/openapi.json`, `/openapi/fr/openapi.json`, `/openapi/es/openapi.json`, `/openapi/openapi.json`, `/openapi/zh/discovery-openapi.json`, `/openapi/fr/discovery-openapi.json`, `/openapi/es/discovery-openapi.json`, `/openapi/discovery-openapi.json`, `/openapi/zh/static-export-openapi.json`, `/openapi/fr/static-export-openapi.json`, `/openapi/es/static-export-openapi.json`, `/openapi/static-export-openapi.json`. Use them to answer questions about endpoints, request/response schemas, parameters, and authentication. Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.