Mintlify Docs MCP 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南
Mintlify 公开文档 MCP 服务器,免登录。AI 代理无需密钥即可搜索 Mintlify 文档、API 指南与组件参考。
本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。
- 提供方
- Mintlify ↗
- 分类
- 🔍 搜索与文档
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"mintlify-docs": {
"url": "https://www.mintlify.com/docs/mcp"
}
}
}claude mcp add --transport http mintlify-docs https://www.mintlify.com/docs/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"mintlify-docs": {
"type": "http",
"url": "https://www.mintlify.com/docs/mcp"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://www.mintlify.com/docs/mcp - No authentication needed — tools are available immediately.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"mintlify-docs": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://www.mintlify.com/docs/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"mintlify-docs": {
"serverUrl": "https://www.mintlify.com/docs/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"mintlify-docs": {
"url": "https://www.mintlify.com/docs/mcp"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.mintlify-docs] url = "https://www.mintlify.com/docs/mcp"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"mintlify-docs": {
"type": "streamableHttp",
"url": "https://www.mintlify.com/docs/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"mintlify-docs": {
"httpUrl": "https://www.mintlify.com/docs/mcp"
}
}
}🧰 Mintlify Docs MCP 工具与 Schema(3)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| search_mintlify ~229 tok | 🟢 Readidempotent | Search across the Mintlify knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Mintlify, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`). | query*: stringlanguage: string |
| query_docs_filesystem_mintlify ~867 tok | 🟢 Readidempotent | 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, 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/discovery-openapi.json | jq '.paths | keys'` — list OpenAPI endpoints OpenAPI specs for this site are mounted under `/openapi`; run `find /openapi -type f` to list them. 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`. | command*: string |
| submit_feedback ~203 tok | 🟠 Writeopen-world | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. | path*: stringfeedback*: string |
🛡️ 安全评级、质量与上下文 Token 审计
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- Public read-only-friendly endpoint — no credentials stored client-side
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 与安全
- 认证方式
- 免密公开
- 动态客户端注册(DCR)
- —
- PKCE S256
- —
- 受保护资源元数据
- https://www.mintlify.com/.well-known/oauth-protected-resource
📡 官方远程端点与传输协议
远程端点 https://www.mintlify.com/docs/mcp 采用 Streamable HTTP(流式 HTTP,2025-03-26 规范)。Streamable HTTP 在单一 POST 端点上完成 JSON-RPC 双向交互,是当前 MCP 规范推荐的传输方式,可直接被 Claude、Cursor、VS Code 等客户端以 URL 形式接入,无需 npx mcp-remote 桥接。
接入前可将端点粘贴至本站 在线 MCP Inspector 实测 initialize / tools/list 握手,确认真实协议行为。
🔐 认证与权限机制
认证方式为 免密公开(None)。完全免密公开,直接粘贴 URL 即可使用——适合文档检索与公开数据查询类场景。
🛡️ 上下文开销与安全审计
该服务端当前登记 3 个工具,全部定义合计约 1319 tokens,会在每次请求时注入模型系统提示词。安全评级为 A+,官方直营来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。
🧩 主流客户端快速接入
本站为 Mintlify Docs MCP 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。代表性工具包括 search_mintlify、query_docs_filesystem_mintlify、submit_feedback 等。
📖 Mintlify Docs 详解
Mintlify Docs MCP — Remote MCP Server
Every Mintlify-hosted docs site can expose an auto-generated MCP endpoint — mintlify.com/docs/mcp is Mintlify eating its own dog food: a public, read-only search over their documentation set, perfect for testing your MCP client config.
Official Mintlify Docs MCP Endpoint & Transport Architecture
- Endpoint URL:
https://www.mintlify.com/docs/mcp - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. Mintlify Docs MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
Mintlify Docs MCP is public and unauthenticated — no OAuth, no API key, no headers. Any MCP client can connect and call its tools directly, which also makes it a great endpoint for smoke-testing your own MCP client or proxy.
All 4 cataloged tools are read-only — Mintlify Docs MCP cannot mutate your account data, which makes it safe to connect broadly.
Common Troubleshooting & Connection Tips
- "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely. - Read-only public docs search — use it to smoke-test client connectivity.
- The same pattern applies to other Mintlify-hosted docs (docs.tavily.com/mcp etc.).
🚀 如何接入 Mintlify Docs MCP 远程 MCP
- 获取远程端点 — 复制官方端点 https://www.mintlify.com/docs/mcp。
- 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL(见下方分客户端指南)。
- 授权并验证 — 保存配置后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。
🔌 Mintlify Docs × 各客户端连接指南
❓ 常见问题
Mintlify Docs MCP 远程 MCP 服务器是官方提供的吗?
本条目标记为「官方直营」。端点由 Mintlify 官方运营,所有收录端点均经过真实 MCP initialize 握手验证。
如何在 Claude / Cursor 中连接 Mintlify Docs MCP?
复制远程端点 https://www.mintlify.com/docs/mcp:Claude Code 执行 claude mcp add --transport http mintlify-docs https://www.mintlify.com/docs/mcp;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "mintlify-docs": { "url": "https://www.mintlify.com/docs/mcp" } } }。
连接时返回 401 或需要密钥怎么办?
该端点免密公开;若仍返回 401 请确认 URL 未拼写错误,并在 Inspector 中重试。
本地 stdio MCP 和这个远程 MCP 有什么区别?
本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 Mintlify 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。