← Back to directory
G

GitMCP

Community
Free, open-source remote MCP server that turns any GitHub project into an AI-queryable documentation hub
GitHub source repository ↗
★ 8.3k Stars Category · Dev Tools Very popular Source revision c487a29895dc
67FMRS · C
Reliability
9/20
Security and permissions
13/20
Maintenance
15/20
Documentation
16/20
Setup experience
14/20

GitMCP is a free, open-source remote MCP server focused on eliminating AI code hallucinations by giving popular AI coding tools smart, read-only access to any GitHub project's documentation and code. It's simple to set up with no authentication, but is limited to public, read-only content and does not support write operations or private repository access.

Read the FMRS scoring method →

GitMCP is a free, open-source, remote Model Context Protocol server that turns any GitHub repository or GitHub Pages site into a documentation hub AI assistants (Cursor, Claude Desktop, Windsurf, and others) can query. It prioritizes a project's llms.txt file, falls back to an AI-optimized documentation version, and finally to README.md, giving AI tools access to up-to-date, accurate documentation and code so they hallucinate less. GitMCP offers per-repository endpoints (gitmcp.io/{owner}/{repo}) for targeted, secure access, plus a generic dynamic endpoint (gitmcp.io/docs) that lets the AI pick the repository at request time. It requires zero setup — no downloads, installs, signups, or authentication — and can also be self-hosted.

Tools

fetch_documentation
Retrieves a GitHub repository's primary documentation (llms.txt first, then an AI-optimized version, then README), giving the AI a project overview.
search_documentation
Runs an intelligent search over a repository's documentation for a given query, returning only relevant parts instead of loading everything.
fetch_url_content
Fetches content from external links referenced in a repository's documentation and converts it into an AI-readable format.
search_code
Searches a repository's actual source code via GitHub code search to find implementation examples or technical details.

Setup

  1. Pick the GitMCP endpoint to use: a specific-repository endpoint at https://gitmcp.io/{owner}/{repo} (or {owner}.gitmcp.io/{repo} for GitHub Pages sites), or the dynamic https://gitmcp.io/docs endpoint to let the AI choose the repository at query time.
  2. Add that URL to your AI client's MCP configuration — Cursor, Windsurf, VS Code, and Cline accept the URL directly (url/serverUrl field); Claude Desktop, Augment Code, and Msty AI connect through npx mcp-remote <url> as the launch command.
  3. Save the configuration and restart/reload the client to confirm the MCP server connects.
  4. Ask the AI assistant documentation- or code-related questions about the target repository to trigger tool calls (usually requiring your approval).
  5. To self-host, clone the repository, run pnpm install, then pnpm dev, and test locally with the MCP Inspector over SSE transport.
claude_desktop_config.json
{
  "mcpServers": {
    "gitmcp": {
      "url": "https://gitmcp.io/{owner}/{repo}"
    }
  }
}

Fit and risk

Best for

  • Developers using MCP-capable AI coding tools like Cursor, Claude Desktop, Windsurf, or VS Code
  • Users who frequently need up-to-date docs/code from one or many public GitHub projects
  • Teams wanting a zero-install, zero-config remote documentation service

Not for

  • Accessing private repositories or content requiring authentication (GitMCP only serves publicly available content and has no auth)
  • Users who need write access — creating commits, PRs, or issues — since GitMCP only provides read-only documentation/code retrieval
  • AI tools that don't support the Model Context Protocol

Required permissions

  • No GitHub authentication required; only accesses content that is already publicly available
  • Respects robots.txt directives when accessing GitHub Pages sites
  • Runs as a remote cloud service, so the client must be allowed to make outbound network requests (tool calls typically require user approval)

Risks and side effects

  • As a third-party remote service, GitMCP explicitly states it is not affiliated with GitHub or any AI tool vendor, so trust in the hosted service should be evaluated independently
  • The fetch_url_content tool may retrieve third-party external links referenced in a repo's docs, so content quality/safety depends on the original source
  • The maintainers state no personal data or queries are stored, but users relying on external hosted infrastructure should weigh this against their own compliance needs

Troubleshooting

  1. Verify the URL format matches the intended mode (specific-repository endpoint vs. dynamic gitmcp.io/docs endpoint)
  2. For clients requiring explicit transport configuration, confirm SSE is set correctly (e.g., "type": "sse" in VS Code's mcp.json)
  3. For clients that bridge via `npx mcp-remote` (e.g., Claude Desktop), ensure Node.js/npx is installed and the machine can reach gitmcp.io
  4. Use the MCP Inspector locally with SSE transport to confirm tools return documentation as expected during development

Use cases

Give an AI coding assistant up-to-date documentation for a library before it generates code, reducing incorrect API usage
Get accurate usage details for niche, new, or fast-changing libraries not covered in the model's training data
Chat directly with a specific repository's documentation from within an IDE via GitMCP's embedded chat
Add a GitMCP badge to your own open-source project's README to show documentation access counts and make it easy for others to connect

Supported clients

CursorFull support
Claude DesktopFull support
WindsurfFull support
VS CodeFull support
ClineFull support
Highlight AIFull support
Augment CodeFull support
Msty AIFull support