Skip to main content
Gemini CLI supports stdio and Streamable HTTP servers, OAuth discovery, MCP tools, resources, and prompts. The client starts the MoleSignal CLI, which carries the messages to MoleSignal. It needs Node.js 20 or later.
1

Sign in once

The browser opens on MoleSignal to approve the sign-in; the CLI keeps it and renews it.
2

Add MoleSignal

Where no browser is at hand, set MOLESIGNAL_URL and MOLESIGNAL_TOKEN (an API token) in the server’s environment instead of signing in. See Connect over stdio. The sections below connect over Streamable HTTP, without the CLI.

​
Connect with OAuth 2.1

1

Add MoleSignal

Omit --scope user to keep the entry in the current project’s .gemini/settings.json.
2

Authenticate

Start an interactive Gemini CLI session, then run:
Complete the browser authorization flow. Gemini CLI discovers the OAuth endpoints and performs dynamic client registration automatically.
3

Verify the server

Run /mcp inside the interactive session to inspect connected tools, resources, and prompts.

​
Configure with JSON

The equivalent Streamable HTTP entry in ~/.gemini/settings.json or .gemini/settings.json is:
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.
Last modified on October 18, 2026