Skip to main content
Use this guide when you want to connect GitHits to a remote MCP client. Remote MCP is not limited to coding agents: it works with any MCP-capable client that supports remote servers. GitHits remote MCP server URL:
For supported local tools, you can use Automatic local MCP setup instead.

Generic remote MCP setup

Use this generic flow when your MCP client supports remote servers but is not listed in the tool-specific examples below.
1

Locate your client's MCP configuration

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

Add the GitHits MCP server entry

Add the remote GitHits MCP server URL to your client’s MCP config. Many clients use this shape:
Some clients require an explicit HTTP type:
VS Code-style configs often use servers instead of mcpServers:
Key names like mcpServers, servers, url, or serverUrl may differ in your client. Check your client’s MCP documentation to confirm the exact schema before saving the config.
3

Verify the connection

Restart your client or reload its MCP server list. If your client supports MCP OAuth, complete the GitHits authorization prompt. Confirm that githits appears as a connected server, then ask it to inspect package context. It should call a GitHits tool such as search, code_read, docs_list, or pkg_info and return a result.

Tool-specific remote setup

Use these examples when you want to add the hosted GitHits MCP server directly to a coding harness.

Codex CLI

Run:
If GitHits asks for OAuth authorization, run:
Open Codex and run /mcp to confirm that githits is connected.

Pi

Install the MCP adapter package:
Then add GitHits to .mcp.json for the current project, or ~/.config/mcp/mcp.json for user-global setup:
Restart Pi after installing the adapter. Use /mcp inside Pi to inspect the server or complete authentication.

Claude Code

Run:
If GitHits asks for OAuth authorization, run:
You can also open Claude Code and run /mcp to complete authentication in the interactive MCP panel.

Gemini CLI

Run:
Gemini CLI stores MCP servers in settings.json. Use /mcp inside Gemini CLI to inspect the server after adding it.

VS Code / GitHub Copilot

Run:
You can also open the Command Palette and run MCP: Add Server, then choose an HTTP server and enter the GitHits URL.

Cursor

Cursor and Cursor CLI use the same MCP configuration. Add GitHits to ~/.cursor/mcp.json for global use, or .cursor/mcp.json for the current project:
In Cursor CLI, run agent mcp list to verify that the server is available.

OpenCode

Run the interactive MCP wizard:
Choose a remote server and enter https://mcp.githits.com. You can also add GitHits to opencode.json:

Cline

Run the interactive MCP wizard:
Choose Add server, select Streamable HTTP, and enter https://mcp.githits.com. You can also add GitHits to ~/.cline/mcp.json:

Windsurf / Devin Desktop

Open Settings > Tools > Windsurf Settings > Add Server, or edit ~/.codeium/windsurf/mcp_config.json directly:
Refresh the MCP server list after saving the config.

Hermes Agent

Add GitHits to ~/.hermes/config.yaml, or to $HERMES_HOME/config.yaml if you use a custom Hermes home:
Restart Hermes after saving the config. Hermes opens the OAuth flow on first connect and stores MCP tokens under ~/.hermes/mcp-tokens/.