GitMCP

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "gitmcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://gitmcp.io/docs"
      ]
    }
  }
}

Before you start

• An MCP-capable client (Cursor, Claude Desktop, Claude Code, Windsurf, VS Code, Cline, Highlight AI, Augment Code, Msty, etc.)
• A public GitHub repository or GitHub Pages site to point at (private repos are not supported)
• No account, API key, or token required — the service is free and unauthenticated

About GitMCP

Tools & capabilities (7)

When to use it

• Use it when an LLM keeps inventing API methods for a library and you want answers grounded in the real repo docs.
• Use it when you're working against a fast-moving or niche library whose docs postdate the model's training cutoff.
• Use it when you want zero local setup — a single SSE URL added to your client.
• Use it when you want the assistant to grep a project's actual source code, not just its prose docs.
• Use it via the generic gitmcp.io/docs endpoint when you want one server that can target any repo you mention mid-chat.

Quick setup

1. 1Pick your endpoint: repo-specific `https://gitmcp.io/{owner}/{repo}`, GitHub Pages `https://{owner}.gitmcp.io/{repo}`, or generic `https://gitmcp.io/docs`.
2. 2Open your MCP client's config and add a new remote/SSE server pointing at that URL.
3. 3Save and restart (or reload) the client so it discovers the GitMCP tools.
4. 4Confirm the `fetch_*_documentation` / `search_*` tools appear in the client's tool list.
5. 5Ask a question about the target repo and verify the assistant cites the fetched docs.

GitMCP FAQ