The per-repository URL is the safer default: the assistant can only reach that project, which removes the risk of it fetching the wrong library's docs, and the README says so directly. The generic endpoint buys flexibility at the cost of the assistant having to identify the right repository on every request.
A remote server that converts a GitHub project — a repository or its GitHub Pages site — into a documentation endpoint. Point your client at a URL and the assistant can read that project's current docs and code instead of relying on what it was trained on.
- A repository's primary documentation fetched, drawing on files such as `llms.txt` — `fetch_<repo-name>_documentation`
- Targeted search inside that documentation rather than loading all of it, which is what keeps large projects affordable in tokens — `search_<repo-name>_documentation`
- The repository's actual code searched through GitHub code search, for implementation details and examples — `search_<repo-name>_code`
- Links found in the docs followed and converted to readable content — `fetch_url_content`
- Two ways to scope it: a per-repository URL at `gitmcp.io/{owner}/{repo}` or `{owner}.gitmcp.io/{repo}`, which restricts the assistant to that project; or the generic `gitmcp.io/docs`, where the tools are named `fetch_generic_documentation`, `search_generic_documentation` and `search_generic_code` and take the repository as an argument
Nothing to install and no account. Add the URL as a server: Cursor and Windsurf take it directly, Claude Desktop goes through `npx mcp-remote`. It is free and open source, does not collect personal information or store queries, and can be self-hosted.
One command — npx mcp-remote https://gitmcp.io/{owner}/{repo}