> ## 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.

# Manual remote MCP setup

> Configure the hosted GitHits MCP server in any MCP-capable client that supports remote servers.

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:

```text theme={null}
https://mcp.githits.com
```

For supported local tools, you can use [Automatic local MCP setup](/installation/automatic-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.

<Steps>
  <Step title="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`.
  </Step>

  <Step title="Add the GitHits MCP server entry">
    Add the remote GitHits MCP server URL to your client's MCP config. Many clients use this shape:

    ```json theme={null}
    {
      "mcpServers": {
        "githits": {
          "url": "https://mcp.githits.com"
        }
      }
    }
    ```

    Some clients require an explicit HTTP type:

    ```json theme={null}
    {
      "mcpServers": {
        "githits": {
          "type": "http",
          "url": "https://mcp.githits.com"
        }
      }
    }
    ```

    VS Code-style configs often use `servers` instead of `mcpServers`:

    ```json theme={null}
    {
      "servers": {
        "githits": {
          "type": "http",
          "url": "https://mcp.githits.com"
        }
      }
    }
    ```

    <Warning>
      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.
    </Warning>
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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:

```bash theme={null}
codex mcp add githits --url https://mcp.githits.com
```

If GitHits asks for OAuth authorization, run:

```bash theme={null}
codex mcp login githits
```

Open Codex and run `/mcp` to confirm that `githits` is connected.

### Pi

Install the MCP adapter package:

```bash theme={null}
pi install npm:pi-mcp-adapter
```

Then add GitHits to `.mcp.json` for the current project, or `~/.config/mcp/mcp.json` for user-global setup:

```json theme={null}
{
  "mcpServers": {
    "githits": {
      "url": "https://mcp.githits.com"
    }
  }
}
```

Restart Pi after installing the adapter. Use `/mcp` inside Pi to inspect the server or complete authentication.

### Claude Code

Run:

```bash theme={null}
claude mcp add --transport http --scope user githits https://mcp.githits.com
```

If GitHits asks for OAuth authorization, run:

```bash theme={null}
claude mcp login githits
```

You can also open Claude Code and run `/mcp` to complete authentication in the interactive MCP panel.

### Gemini CLI

Run:

```bash theme={null}
gemini mcp add --transport http --scope user githits https://mcp.githits.com
```

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:

```bash theme={null}
code --add-mcp '{"name":"githits","type":"http","url":"https://mcp.githits.com"}'
```

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:

```json theme={null}
{
  "mcpServers": {
    "githits": {
      "url": "https://mcp.githits.com"
    }
  }
}
```

In Cursor CLI, run `agent mcp list` to verify that the server is available.

### OpenCode

Run the interactive MCP wizard:

```bash theme={null}
opencode mcp add
```

Choose a remote server and enter `https://mcp.githits.com`.

You can also add GitHits to `opencode.json`:

```json theme={null}
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "githits": {
      "type": "remote",
      "url": "https://mcp.githits.com",
      "enabled": true
    }
  }
}
```

### Cline

Run the interactive MCP wizard:

```bash theme={null}
cline mcp
```

Choose **Add server**, select **Streamable HTTP**, and enter `https://mcp.githits.com`.

You can also add GitHits to `~/.cline/mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "githits": {
      "type": "streamableHttp",
      "url": "https://mcp.githits.com",
      "disabled": false,
      "autoApprove": []
    }
  }
}
```

### Windsurf / Devin Desktop

Open **Settings** > **Tools** > **Windsurf Settings** > **Add Server**, or edit `~/.codeium/windsurf/mcp_config.json` directly:

```json theme={null}
{
  "mcpServers": {
    "githits": {
      "serverUrl": "https://mcp.githits.com"
    }
  }
}
```

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:

```yaml theme={null}
mcp_servers:
  githits:
    url: "https://mcp.githits.com"
    auth: oauth
```

Restart Hermes after saving the config. Hermes opens the OAuth flow on first connect and stores MCP tokens under `~/.hermes/mcp-tokens/`.