GitMCP

At a glance

GitMCP runs in the cloud, so there is nothing to install: you add a URL. Point it at one repository (gitmcp.io/owner/repo) and the assistant gets tools to fetch that project's documentation, search it and search its code. Use the generic address, gitmcp.io/docs, and the model picks the repository itself for each question.

It reads llms.txt first when a project has one, then the README. That makes it a light, free way to stop a model guessing at a library it knows badly, without any account.

Made by

The GitMCP project (idosal/git-mcp), free and open source

GitHub stars

8.5K

Downloads

33 a week

Last commit

8 May 2026

Tools

5

Runs on

Hosted

Our check: It needs something our Linux test machine does not have (an account, a desktop app, a Mac or a running service), so on 27 Oct 2026 we read its tools from the source code instead of running this config. The npm package called "git-mcp" has no link to this project. GitMCP is a hosted service; the repository is its source, for anyone who wants to run their own copy.

What's in the pod: its tools

We found 5 tools in its source code on 27 Oct 2026. Every one of them only reads, so nothing changes unless you act on what it finds.

How we tested it: Read from the GitMCP source for the generic /docs address. Our test network could not reach gitmcp.io. A repository address such as gitmcp.io/owner/repo names the tools after that repository instead.

Grouped and described by us. The README on GitHub lists the inputs each tool takes.

Set it up

Pick your app for the exact snippet and where it goes.

https://gitmcp.io/docs

claude mcp add --transport http gitmcp https://gitmcp.io/docs

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

{
  "servers": {
    "gitmcp": {
      "type": "http",
      "url": "https://gitmcp.io/docs"
    }
  }
}

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

https://gitmcp.io/docs

Swap /docs for /owner/repo (for example https://gitmcp.io/microsoft/playwright-mcp) to lock it to one project and get tools named after it.

New to this? See the setup guides for Claude Code, Cursor, Claude Desktop and ChatGPT.

Settings

Names are exactly as the project spells them. Required ones are marked.

What it can touch

Safer setup: Everything it does is read-only. A repository-specific URL keeps the model from wandering to repositories you did not mean.

Before you start

• Nothing: no account, key or install
• A client that can connect to a remote URL (or mcp-remote as a bridge)

If it does not work

The model picks the wrong repository

Use the repository-specific address instead of /docs, or name owner/repo in your prompt.

Answers are thin for a project

GitMCP reads llms.txt first, then the README. Projects with little written documentation give it little to work with; search_generic_code can still find examples in the source.

Private repositories do not work

The hosted service only reads public repositories. For private code, use the GitHub MCP server with a token instead.

Peas in a pod: similar servers

How GitMCP lines up against other developer tools servers on the shelf.

Questions

Something wrong on this page? Tell us.