git

GitMCP turns any GitHub repository or GitHub Pages site into a live documentation hub that AI tools can query via MCP. By pointing your MCP-enabled assistant at a GitMCP URL (for example, gitmcp.io/{owner}/{repo} or the dynamic https://gitmcp.io/docs), you enable the AI to fetch up-to-date docs and code examples directly from the source, reducing hallucinations and increasing accuracy. The server supports integration with popular tools and editors such as Cursor, Claude Desktop, Windsurf, VSCode, Highlight AI, Augment Code, and Msty AI, allowing you to configure a consistent MCP endpoint across multiple environments. Use the provided configurations to connect your assistant to a specific repository or to the generic docs endpoint for flexible access to multiple projects.

Prerequisites:

• Node.js (including npm or npx) installed on your machine or environment where you plan to run MCP commands.

Step-by-step installation:

1. Ensure Node.js is installed. Verify with: node -v npm -v

2. You do not install a server directly in this setup. Instead, use the MCP remote launcher via npx to connect to GitMCP endpoints. The typical usage is: npx mcp-remote https://gitmcp.io/{owner}/{repo}

3. (Optional) If you want to pin a specific repository, replace {owner} and {repo} with the target GitHub user/organization and repository name. For example: npx mcp-remote https://gitmcp.io/facebook/react

4. If you prefer configuring via a local tool, you can store the MCP server config in your editor or IDE as demonstrated in the README examples (Cursor, Claude, Windsurf, VSCode, etc.).

Tips and common considerations:

• The GitMCP server is accessed via the mcp-remote npm package. The most common invocation is npx mcp-remote https://gitmcp.io/{owner}/{repo} or https://gitmcp.io/docs for a generic, repository-agnostic endpoint.
• When connecting with IDEs, ensure you replace {owner} and {repo} with the actual GitHub identifiers.
• If you encounter connectivity issues, verify you can reach https://gitmcp.io and that your network allows SSE or the relevant protocol used by your integration.
• The mcp_config uses the server key gitmcp; you can rename or duplicate entries to support multiple repositories or endpoints.
• There are no mandatory environment variables for the standard usage, but some environments may require proxies or authentication tokens depending on your network setup.