Server facts
GitMCP MCP Server
Project
- Author
- idosal
- Repository
- github.com/idosal/git-mcp
- Website
- gitmcp.io
- License
- Apache-2.0
- Category
- Developer Tools
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 8,465
- Last commit
- Data as of
Tags
- Code Search
- Coding Agents
- Documentation
- Github
- Remote Mcp
Overview
GitMCP is a remote documentation integration for public GitHub projects and GitHub Pages sites. It lets an assistant fetch primary documentation, search relevant passages, follow links mentioned in documentation, and search repository code. The intent is to ground answers about libraries and implementations in source material rather than relying entirely on the model's prior knowledge. Users can connect to a particular repository for focused access or choose a generic endpoint that selects a repository for each request. The README explains that the generic route offers flexibility but depends on identifying the intended project correctly.
The hosted service is described as free and does not require signup, local installation, or repository changes. MCP clients can connect directly to a URL, while clients such as Claude Desktop can use an npx mcp-remote bridge. Documentation retrieval prioritizes llms.txt, then AI-oriented project documentation, and finally README or root content. GitMCP also offers an embedded browser chat and can be self-hosted. Its privacy section says it does not collect personal information, retain agent queries, or permanently store project content. Access is limited to publicly available material and happens on request; GitHub Pages access respects robots.txt directives. This makes GitMCP a fit for coding assistants that need current public project context, not an authenticated interface for modifying repositories or managing issues.
Install & configure
Requirements
- An MCP-compatible client
- A public GitHub repository or GitHub Pages project
- npx when using the documented local bridge
npx mcp-remote 'https://gitmcp.io/{owner}/{repo}'Replace {owner} and {repo} with the desired public project's identifiers. This command is the README's bridge configuration, not a locally hosted GitMCP server. Direct SSE clients can use the URL; https://gitmcp.io/docs is the documented dynamic alternative. Tool names for repository-specific access are reproduced as shown in the supplied README.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
A supported configuration example is not available for this client and transport. Check the client documentation for its connection flow; do not substitute an undocumented JSON format.
Read the Claude Desktop setup guideConfig file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"git-mcp": {
"url": "https://gitmcp.io/%7Bowner%7D/%7Brepo%7D"
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
A supported configuration example is not available for this client and transport. Check the client documentation for its connection flow; do not substitute an undocumented JSON format.
Read the VS Code setup guideConfig file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"git-mcp": {
"serverUrl": "https://gitmcp.io/%7Bowner%7D/%7Brepo%7D"
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"git-mcp": {
"type": "sse",
"url": "https://gitmcp.io/%7Bowner%7D/%7Brepo%7D"
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| fetch__documentation | Retrieve the repository's primary documentation, prioritizing sources such as llms.txt. |
| search__documentation | Find relevant passages in repository documentation using a query. |
| fetch_url_content | Read linked reference content in a format suitable for an assistant. |
| search__code | Find repository implementation examples through GitHub code search. |
| fetch_generic_documentation | Fetch documentation for a specified repository through the dynamic endpoint. |
| search_generic_code | Search a specified repository's code through the dynamic endpoint. |
| search_generic_documentation | Search documentation for a selected repository through the generic server. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Ask an assistant how to use a public GitHub library.
- Search repository documentation for a particular API or concept.
- Find implementation examples in public project code.
- Switch between repository documentation sources through the dynamic endpoint.
- Follow external references mentioned in project documentation.
Strengths
- Hosted use requires no signup or repository modification.
- Offers focused repository endpoints and a flexible generic endpoint.
- Documents privacy limits and supports independent self-hosting.
Limitations
- Access is limited to publicly available content.
- The generic endpoint depends on choosing the intended repository correctly.
- GitHub Pages retrieval follows robots.txt restrictions.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
