GitMCP MCP server for Claude, Codex and Cursor

What your AI apps can do with GitMCP

Fetch project documentation
Search repository code

GitMCP MCP tools

5 tools, listed by Toolstile from the server itself on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`match_common_libs_owner_repo_mapping`	Match a library name to an owner/repo. Don't use it if you have an owner and repo already. Use this first if only a library name was provided. If found - you can use owner and repo to call other tools. If not found - try to use the library name directly in other tools.
`fetch_generic_documentation`	Fetch documentation for any GitHub repository by providing owner and project name
`search_generic_documentation`	Semantically search in documentation for any GitHub repository by providing owner, project name, and search query. Useful for specific queries.
`search_generic_code`	Search for code in any GitHub repository by providing owner, project name, and search query. Returns matching files. Supports pagination with 30 results per page.
`fetch_generic_url_content`	Generic tool to fetch content from any absolute URL, respecting robots.txt rules. Use this to retrieve referenced urls (absolute urls) that were mentioned in previously fetched documentation.

Suggested access for each AI app

GitMCP's server doesn't mark its tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same GitMCP connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add GitMCP to a workspace (no sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every GitMCP tool, give Cursor only the read tools, or keep GitMCP away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the GitMCP MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect GitMCP in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the GitMCP endpoint to each app separately. In Claude Code:

Shell

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

In Cursor's mcp.json:

JSON

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

Some servers accept only clients they have approved, or need a token header. Check the GitMCP MCP documentation for what your client needs.

Before you connect

No account needed.

Server details

Detail	Value
Publisher	GitMCP
Endpoint	`https://gitmcp.io/docs`
Authentication	No sign-in
Categories	Development
Tool list	5 tools, observed 29 October 2026 (discovery)

GitMCP MCP documentation