fetch_<repo-name>_documentationLABSCO SUMMARY
Pin it to one repository unless you really need to switch.
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.
What it is
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.
What you get
- 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 genericgitmcp.io/docs, where the tools are namedfetch_generic_documentation,search_generic_documentationandsearch_generic_codeand take the repository as an argument
Requirements
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.
Setup effort
Get your endpoint, then paste it — add your endpoint to your client
USE CASES
01
Coding against a library the model does not know
Add that repository's URL and let the assistant read the current documentation before writing anything, instead of inventing an API from a stale memory.
02
Finding how something is actually used
Search the repository's code for the pattern rather than the prose — implementations and real call sites, not just what the docs claim.
03
Working with a large project without burning the context window
Search the documentation with a query so only the relevant sections come back, instead of fetching everything.
04
Jumping between several libraries in one session
Use the generic endpoint and name the repository per request — flexible, at the cost of the assistant having to pick the right project each time.
7 tools
Listed in project docs. Your client may show a different list.
search_<repo-name>_documentationsearch_<repo-name>_codefetch_url_contentfetch_generic_documentationsearch_generic_documentationsearch_generic_codeBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"gitmcp": {
"url": "https://gitmcp.io/<YOUR_OWNER>/<YOUR_REPO>"
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"gitmcp": {
"command": "npx",
"args": [
"mcp-remote",
"https://gitmcp.io/<YOUR_OWNER>/<YOUR_REPO>"
]
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"gitmcp": {
"serverUrl": "https://gitmcp.io/<YOUR_OWNER>/<YOUR_REPO>"
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"gitmcp": {
"type": "sse",
"url": "https://gitmcp.io/<YOUR_OWNER>/<YOUR_REPO>"
}
}
}Cline
CLINE · JSON
{
"mcpServers": {
"gitmcp": {
"type": "streamableHttp",
"url": "https://gitmcp.io/<YOUR_OWNER>/<YOUR_REPO>",
"disabled": false,
"autoApprove": []
}
}
}Highlight AI
Plugin name: gitmcp
SSE URL: https://gitmcp.io/{owner}/{repo}
Augment Code, Msty AI
JSON
{
"mcpServers": {
"git-mcp Docs": {
"command": "npx",
"args": [
"mcp-remote",
"https://gitmcp.io/<YOUR_OWNER>/<YOUR_REPO>"
]
}
}
}
