GitMCP Docs MCP 远程 MCP 服务器 – 官方端点、工具列表与一键连接指南

🧑‍💻 Community✓ VerifiedStreamable HTTPPublic · No Auth🛡️ A+~740 tok5 tools·Online457ms·30 天在线率: 100%·上次拨测 2 分钟前

GitMCP 社区 MCP 服务器,公开免登录。AI 代理可为任意公开 GitHub 仓库搜索和拉取最新文档。

本页收录其官方远程端点、传输协议、认证方式、全部工具 Schema、实时可用性拨测与安全审计结果,并为 Cursor、Claude Code、VS Code、ChatGPT 等 10 大客户端提供一键接入指引。

https://gitmcp.io/docs
提供方
GitMCP ↗
分类
🔍 搜索与文档🛠️ 开发者工具与 Git
Streamable HTTPhttps://gitmcp.io/docs
Install in Cursor →

Or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "gitmcp": {
      "url": "https://gitmcp.io/docs"
    }
  }
}

🧰 GitMCP Docs MCP 工具与 Schema(5)

ToolSafetyDescriptionParameters
match_common_libs_owner_repo_mapping
~147 tok
🟠 WriteMatch a library name to an owner/repo. Don't use it if you have an owner and repo already. Use this first if only a library name was provided. If found - you can use owner and repo to call other tools. If not found - try to use the library name directly in other tools.library*: string
fetch_generic_documentation
~115 tok
🟢 ReadFetch documentation for any GitHub repository by providing owner and project nameowner*: stringrepo*: string
search_generic_documentation
~155 tok
🟢 ReadSemantically search in documentation for any GitHub repository by providing owner, project name, and search query. Useful for specific queries.owner*: stringrepo*: stringquery*: string
search_generic_code
~185 tok
🟢 ReadSearch for code in any GitHub repository by providing owner, project name, and search query. Returns matching files. Supports pagination with 30 results per page.owner*: stringrepo*: stringquery*: stringpage: number
fetch_generic_url_content
~118 tok
🟢 ReadGeneric tool to fetch content from any absolute URL, respecting robots.txt rules. Use this to retrieve referenced urls (absolute urls) that were mentioned in previously fetched documentation.url*: string

🛡️ 安全评级、质量与上下文 Token 审计

🛡️ 安全评级 A+上下文 Token 开销: ~740 tokens(该服务端 5 个工具定义注入每次系统提示词)

估算单次调用 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
  • Community-operated endpoint
  • Manually verified by RemoteMCP.net

🔐 OAuth 2.1 与安全

认证方式
免密公开
动态客户端注册(DCR)
—
PKCE S256
—
受保护资源元数据
https://gitmcp.io/.well-known/oauth-protected-resource
审计 OAuth 2.1 配置 →

📡 官方远程端点与传输协议

远程端点 https://gitmcp.io/docs 采用 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 即可使用——适合文档检索与公开数据查询类场景。

🛡️ 上下文开销与安全审计

该服务端当前登记 5 个工具,全部定义合计约 740 tokens,会在每次请求时注入模型系统提示词。安全评级为 A+,社区维护来源。工具名与 Schema 越精简,对上下文窗口的"税"越低;可用 feecalculator.app 估算每次调用的边际成本。

🧩 主流客户端快速接入

本站为 GitMCP Docs MCP 生成了 Cursor / Claude Code / VS Code / ChatGPT / Windsurf / Kiro / Codex / Cline / Gemini 等 10 大客户端的专属配置——包括一键 deeplink、claude mcp add 命令与 JSON/TOML 片段。下方选择你的客户端即可查看 1 分钟接入步骤。代表性工具包括 match_common_libs_owner_repo_mapping、fetch_generic_documentation、search_generic_documentation、search_generic_code、fetch_generic_url_content 等。

📖 GitMCP Docs 详解

GitMCP Docs MCP — Remote MCP Server

GitMCP answers the stale-docs problem: point it at any public repo and get semantic search plus raw fetch over its README, docs/ and wiki — always current with the default branch. Completely public, which also means you should not rely on it for private or SLA-bound workflows.

Official GitMCP Docs MCP Endpoint & Transport Architecture

  • Endpoint URL: https://gitmcp.io/docs
  • 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. GitMCP Docs MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.

Authentication, Scopes & Permission Boundaries

GitMCP 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 — GitMCP 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-send initialize; stateless clients can ignore session headers entirely.
  • Community-operated — treat availability as best-effort.
  • Per-repo endpoints also exist (gitmcp.io//) for scoped doc search.

🚀 如何接入 GitMCP Docs MCP 远程 MCP

  1. 获取远程端点 — 复制官方端点 https://gitmcp.io/docs。
  2. 写入客户端配置 — 在 Cursor 的 mcp.json / Claude Code CLI / 其他客户端中添加该 URL(见下方分客户端指南)。
  3. 授权并验证 — 保存配置后,在本站 Inspector 中运行 initialize 与 tools/list 验证连通性。

🔌 GitMCP Docs × 各客户端连接指南

❓ 常见问题

GitMCP Docs MCP 远程 MCP 服务器是官方提供的吗?

本条目标记为「社区维护」。端点由第三方社区运营,并非 GitMCP 直营,所有收录端点均经过真实 MCP initialize 握手验证。

如何在 Claude / Cursor 中连接 GitMCP Docs MCP?

复制远程端点 https://gitmcp.io/docs:Claude Code 执行 claude mcp add --transport http gitmcp https://gitmcp.io/docs;Cursor 可直接使用本页的一键 deeplink 或在 ~/.cursor/mcp.json 中添加 { "mcpServers": { "gitmcp": { "url": "https://gitmcp.io/docs" } } }。

连接时返回 401 或需要密钥怎么办?

该端点免密公开;若仍返回 401 请确认 URL 未拼写错误,并在 Inspector 中重试。

本地 stdio MCP 和这个远程 MCP 有什么区别?

本地 MCP 通过 npx/uvx 在你的机器上启动 stdio 子进程,依赖本地运行时且密钥以明文写入配置文件;远程 MCP 是 GitMCP 托管的 HTTPS 端点,免安装、支持 OAuth 2.1 授权流,且同一端点可跨桌面与移动端复用。详见 本地 vs 远程 MCP 对比。

🔗 同类远程 MCP 服务端