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.

There is one MCP installation path for GitHits: the hybrid CLI. 
npx githits@latest init
If your AI coding tool is supported, init detects it and writes the MCP configuration automatically. If your tool is not auto-configured, add the same MCP server manually with the config below.

​
How to configure GitHits manually

1

Locate your tool's MCP configuration

Find the file or settings panel where your tool accepts MCP server definitions. The exact name and location varies by tool — check your tool’s documentation for details. Common key names include mcpServers, mcp, or servers.
2

Add the GitHits MCP server entry

Add the following configuration to your tool’s MCP config. This is the universal GitHits MCP server command:
{
  "mcpServers": {
    "githits": {
      "command": "npx",
      "args": ["-y", "githits@latest", "mcp", "start"]
    }
  }
}
Your tool runs this command as a subprocess and communicates with it over stdio. No background service or global install is required.
Key names like mcpServers may differ in your tool. Check your tool’s MCP documentation to confirm the exact schema before saving the config.
3

Verify the connection

Restart your tool (or reload its MCP server list) and confirm that githits appears as a connected server. Then try asking your agent to find a code example — it should call the GitHits get_example tool and return a result.

​
Supported auto-configuration

npx githits@latest init supports automatic install for Claude Code, Cursor, Windsurf, VS Code / Copilot, Cline, Claude Desktop, Codex CLI, Gemini CLI, Google Antigravity, and OpenCode. If you want GitHits init to auto-detect and configure another tool in a future release, open an issue or pull request on github.com/githits-com/githits-cli. Include the tool name and, if possible, the MCP config file path and schema your tool expects.

​
Uninstalling

To remove GitHits MCP configuration from all tools that init configured, run: 
npx githits@latest init uninstall
This removes only the GitHits MCP and plugin configuration entries. It does not delete stored credentials. To also remove stored credentials: 
npx githits@latest logout
For manually configured tools, remove the githits entry you added from your tool’s MCP config file.