Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.githits.com/llms.txt

Use this file to discover all available pages before exploring further.

GitHits previously supported a legacy remote MCP server at https://mcp.githits.com/. It can authenticate with Dynamic Client Registration (DCR) OAuth when your client supports it, or with an API token passed as a bearer token. The recommended setup now uses either local MCP through the GitHits CLI, or GitHits Skills if your harness supports Skills. For local MCP, run: 
npx githits@latest init
Both current paths avoid storing bearer tokens in tool configuration files. Local MCP lets GitHits handle authentication through the CLI. Skills provide the same GitHits workflow through harness instructions instead of MCP tools.
Legacy remote MCP only supports GitHits example search. It does not include the newer code navigation, documentation access, package inspection, vulnerability, dependency, or changelog capabilities. Use local MCP or GitHits Skills for the full current GitHits workflow.

​
What changes

Legacy remote setupCurrent setup
Connects to https://mcp.githits.com/Uses local MCP or GitHits Skills
Uses DCR OAuth or Authorization: Bearer ...Uses CLI-managed authentication or Skills instructions
Often needs per-tool HTTP MCP settingsWorks as a standard stdio MCP server
May use mcp-remote as a proxyDoes not need a proxy

​
Migration steps

1

Remove the legacy MCP server entry

Open your tool’s MCP configuration and remove any GitHits server entry that uses one of these patterns:
{
  "url": "https://mcp.githits.com/"
}

{
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://mcp.githits.com/"]
}
Also remove any GitHits Authorization header or token input tied to that server.
2

Choose local MCP or Skills

Use local MCP when you want your agent to call GitHits MCP tools directly:
npx githits@latest init
Use Skills when your harness has strong Skills support and you prefer instruction-driven workflows:
npx skills add githits-com/githits-cli
Do not use both in the same harness at the same time. They expose overlapping capabilities.
3

Configure local MCP if needed

If your tool is not detected by init, add the local MCP server manually:
{
  "mcpServers": {
    "githits": {
      "command": "npx",
      "args": ["-y", "githits@latest", "mcp", "start"]
    }
  }
}
Some tools use servers instead of mcpServers. Keep the command and args the same, but follow your tool’s schema.
4

Authenticate with the CLI

For normal local setup, init handles authentication. To authenticate separately, run:
npx githits@latest login
For SSH or headless machines, use:
npx githits@latest login --no-browser
5

Restart and verify

Restart your coding tool or reload its MCP server list. Confirm that GitHits appears as a local MCP server, then ask your agent to use GitHits:
Use GitHits Code Examples to find a real open-source implementation of HTTP retries with exponential backoff in Python.
6

Revoke old MCP tokens

After the local setup works, revoke legacy MCP tokens that were used only for https://mcp.githits.com/.Go to app.githits.com, open Settings, then remove tokens under MCP Tokens.

​
Tool-specific replacements

Use these replacements when you are migrating a manually configured tool.

​
VS Code / Copilot

Remove the old HTTP server from .vscode/mcp.json: 
{
  "servers": {
    "GitHits": {
      "url": "https://mcp.githits.com/",
      "type": "http"
    }
  }
}
Replace it with: 
{
  "servers": {
    "githits": {
      "command": "npx",
      "args": ["-y", "githits@latest", "mcp", "start"]
    }
  }
}

​
Cursor, Windsurf, Cline, and similar tools

Remove any GitHits entry that uses url, serverUrl, type: "http", or type: "streamableHttp" with https://mcp.githits.com/. Replace it with: 
{
  "mcpServers": {
    "githits": {
      "command": "npx",
      "args": ["-y", "githits@latest", "mcp", "start"]
    }
  }
}

​
Claude Code

If you added the old remote server with claude mcp add --transport http, remove that server from Claude Code first. Then run: 
npx githits@latest init
Or install the GitHits Claude Code plugin: 
claude plugin marketplace add githits-com/githits-cli
claude plugin install githits@githits-plugins

​
Codex CLI

If you added the old remote server with --url https://mcp.githits.com, remove that entry first. Then add the local server: 
codex mcp add githits -- npx -y githits@latest mcp start

​
When to keep remote MCP

Use the local CLI setup unless your environment specifically requires HTTP MCP and cannot run a local stdio server process. If local MCP is not a fit but your harness supports Skills, use GitHits Skills instead. If you still need remote MCP, prefer DCR OAuth when your MCP client supports it. If you use an API token, keep it in a secret store or environment variable. Do not commit bearer tokens to source control. Remember that remote MCP is a legacy fallback for example search only. It does not provide the full current GitHits workflow available through local MCP or Skills. For authentication details, see Authentication. For the generic local config, see Manual Setup. For Skills setup, see Automatically install GitHits Skills.