> ## Documentation Index
> Fetch the complete documentation index at: https://docs.molesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Gemini CLI

> Connect Gemini CLI to MoleSignal Inbound MCP with Streamable HTTP and automatic OAuth discovery.

Gemini CLI supports Streamable HTTP, OAuth discovery, MCP tools, resources, and prompts.

## Connect with OAuth 2.1

<Steps>
  <Step title="Add MoleSignal">
    ```bash theme={null}
    gemini mcp add --transport http --scope user \
      molesignal https://molesignal.example.com/api/v1/mcp
    ```

    Omit `--scope user` to keep the entry in the current project's `.gemini/settings.json`.
  </Step>

  <Step title="Authenticate">
    Start an interactive Gemini CLI session, then run:

    ```text theme={null}
    /mcp auth molesignal
    ```

    Complete the browser authorization flow. Gemini CLI discovers the OAuth endpoints and
    performs dynamic client registration automatically.
  </Step>

  <Step title="Verify the server">
    ```bash theme={null}
    gemini mcp list
    ```

    Run `/mcp` inside the interactive session to inspect connected tools, resources, and prompts.
  </Step>
</Steps>

## Configure with JSON

The equivalent Streamable HTTP entry in `~/.gemini/settings.json` or
`.gemini/settings.json` is:

```json theme={null}
{
  "mcpServers": {
    "molesignal": {
      "httpUrl": "https://molesignal.example.com/api/v1/mcp"
    }
  }
}
```

Do not set `trust: true` for a managed operations server unless local Gemini policy is intended to
bypass the client's own confirmation prompt. MoleSignal approval policy still applies on the
server.

See the [official Gemini CLI MCP documentation](https://geminicli.com/docs/tools/mcp-server/).