1. Home
  2. GitMCP
  3. GitMCP for Cursor: Setup & Config

Data as of

GitMCP for Cursor: Setup & Config

GitMCP turns public GitHub repositories and GitHub Pages projects into documentation sources for Cursor.

GitMCP Cursor configuration

  1. Choose Cursor configuration scope

    For GitMCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add GitMCP to Cursor

    Use the git-mcp entry below in mcpServers. Keep GitMCP's documented sse connection fields and your other Cursor entries.

  3. Check GitMCP in Cursor

    GitMCP: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "git-mcp": {
      "url": "https://gitmcp.io/%7Bowner%7D/%7Brepo%7D"
    }
  }
}

GitMCP in Cursor: sse checks

  • Enable GitMCP in Cursor's MCP settings and inspect its tools. For gitmcp.io, check reachability, transport, and credential expiry if authentication fails.
  • GitMCP: check sse connectivity to gitmcp.io from Cursor; a stdio command is not a replacement for this endpoint.
Catalog transports
stdio
Tools
fetch__documentation, search__documentation, fetch_url_content

GitMCP — details. Cursor guide

Frequently asked questions

Cursor's GitMCP entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's git-mcp example uses sse. The GitMCP catalog lists stdio; these instructions follow the stored configuration instead.

Cursor connects GitMCP to gitmcp.io using url.

GitMCP's stored list contains 7 tools, including fetch__documentation, search__documentation, fetch_url_content. Compare those names with Cursor's connected tool list; the stored list is not a live check.