Connecting services and preparing your dashboard.
Gemini CLI connects to Zephex over Streamable HTTP with OAuth discovery. The config contains only the MCP URL and transport type, not a Bearer header or pasted API key.
OVERVIEW
Gemini CLI is Google's open-source terminal AI agent backed by Gemini 2.5 Pro. It supports MCP servers via Streamable HTTP and handles OAuth through Dynamic Client Registration auto-discovery. After adding the config, run `/mcp auth zephex` inside a Gemini session to trigger the browser OAuth flow.
CONFIG FILE LOCATION
~/.gemini/settings.json. Global config. Applies to all Gemini CLI sessions.
Paste the JSON exactly as shown under `mcpServers`. Use `url` with `type: http`. The Zephex config contains only the URL and transport because authentication happens through OAuth discovery instead of a pasted key.
Do not add an Authorization header or paste a Zephex API key into this file. Gemini CLI should authenticate from the hosted MCP URL through the browser flow.
{ "mcpServers": { "zephex": { "url": "https://zephex.dev/mcp", "type": "http" } }}Confirm the remote MCP server is loaded before you rely on it in normal prompts.
Make sure the settings file was saved before starting the session, then restart Gemini CLI after editing the config.
Use `url` instead of `httpUrl`. The config on this page already uses the current field names.
Run `/mcp` and check whether the server is authenticated. If it is connected but not authenticated, run `/mcp auth zephex` again.
Update Gemini CLI to the latest version with `npm update -g @google/gemini-cli` and try again.
If the editor still does not connect, return to Quickstart or check Connection Issues.