Skip to main content
Use automatic local MCP setup when your coding tool is supported by the GitHits hybrid CLI.
npx githits@latest init
The CLI detects installed tools and writes the local MCP server configuration for each supported harness. Authentication is handled automatically for common local setup.

Automatic install support

npx githits@latest init supports automatic install for Claude Code, Cursor, Windsurf, VS Code / Copilot, Cline, Claude Desktop, Codex CLI, Pi, Gemini CLI, Google Antigravity, OpenCode, Zed, Junie, Qwen Code, Kiro, Kilo Code, Factory Droid, and Amazon Q CLI.

What gets configured

GitHits adds a local MCP server entry that starts the CLI on demand:
{
  "mcpServers": {
    "githits": {
      "command": "npx",
      "args": ["-y", "githits@latest", "mcp", "start"]
    }
  }
}
Your agent can then call GitHits tools when it needs indexed source, package documentation, dependency metadata, vulnerability data, changelogs, or implementation examples. If it does not choose the tools on its own, use the prompts in Trigger GitHits manually.

Guided MCP setup (default)

Interactive githits init defaults to the recommended Install GitHits MCP + supporting instructions path. In addition to the MCP server entry above, guided setup installs a small amount of supporting context so agents know when to reach for GitHits:
  • githits-mcp skill — a SKILL.md file describing when to prefer GitHits over model memory or generic search, and which tool to pick for docs, source, package metadata, vulnerabilities, changelogs, and cross-project examples. It is copied into the selected tool’s skills folder (for example .claude/skills/githits-mcp/, .cline/skills/githits-mcp/, or .agents/skills/githits-mcp/ when the tool loads shared Agent Skills).
  • Managed instruction block — a single short paragraph inserted between <!-- githits --> markers in the appropriate instruction file for your tool (for example AGENTS.md, CLAUDE.md, or GEMINI.md). Reruns replace only the content between the markers, so it stays idempotent and easy to remove.
Both additions are opt-out. Use --no-guidance to install the plain MCP server only, or pick Install plain GitHits MCP at the interactive prompt:
npx githits@latest init --no-guidance
To keep the guidance files when removing GitHits:
npx githits@latest init uninstall --keep-guidance
If you prefer a skills-only setup with no MCP server, choose Install Agent Skills instead — see Skills.

Want remote MCP instead?

If you want to connect GitHits as a hosted remote MCP server, use Manual remote MCP setup. Remote MCP works with any MCP-capable client that supports remote servers, not just coding agents.