# Connect Gemini CLI

Gemini CLI: The full authenticated connector.

Where it runs: Gemini CLI in the terminal.

## Add the connector

1. Add the server with the http transport:

```text
gemini mcp add --transport http sleeperhit https://sleeperhit.studio/mcp
```
2. Or write it into .gemini/settings.json (project) or ~/.gemini/settings.json — a remote Streamable HTTP server is `httpUrl`:

`.gemini/settings.json`:

```json
{
  "mcpServers": {
    "sleeperhit": {
      "httpUrl": "https://sleeperhit.studio/mcp"
    }
  }
}
```
3. Authorize with /mcp auth in a session (or `gemini mcp` equivalents); check status with `gemini mcp list`.

## Signing in

On a 401, Gemini CLI discovers the OAuth metadata, registers a client when the server supports it, and opens the browser. Tokens are kept in ~/.gemini/mcp-oauth-tokens.json.

The connector itself needs no API key. A brand-new account is confirmed once at signup (18 or older, Terms and Privacy accepted); see [Any other client](connect-any.md) for what a generic client must support.

## Good to know

- Its OAuth callback is fixed to http://localhost:7777/oauth/callback, so sign-in fails in fully headless or remote-SSH setups (no way to paste a callback back).
- Model sign-in for Gemini Code Assist individual accounts changed in October 2026 (the suite moved to Antigravity). That is separate from the Sleeper Hit connector; if your build blocks all MCP use, check the Gemini CLI changelog first.

## Sources for these steps

- https://google-gemini.github.io/gemini-cli/docs/tools/mcp-server.html

The connector URL on this page is the production one; stage members can use `https://stage.sleeperhit.studio/mcp` the same way. The same steps, plus every other MCP client, are on the [connector page](/mcp) on the app host.