Gemini CLI

Gemini CLI connects to Zephex through a local stdio MCP entry. Use the settings JSON below instead of the older hosted HTTP block.

OVERVIEW

Gemini CLI is Google's terminal AI agent. For Zephex, the reliable setup is the local stdio MCP config in `~/.gemini/settings.json` or `<project>/.gemini/settings.json`, running `npx -y zephex` with your `ZEPHEX_API_KEY` in the env block.

CONFIG FILE LOCATION

~/.gemini/settings.json for a global setup, or <project>/.gemini/settings.json for a project-local one.

PREREQUISITES

Gemini CLI installed with `npm install -g @google/gemini-cli` or `npx @google/gemini-cli`.
A Zephex API key from your dashboard.

CONFIG

Paste the JSON exactly as shown under `mcpServers`. Gemini CLI should launch the local `npx -y zephex` process.

Replace `mcp_sk_your_key_here` with your real Zephex API key before saving.

{  "mcpServers": {    "zephex": {      "command": "npx",      "args": ["-y", "zephex"],      "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" }    }  }}

SETUP

Save ~/.gemini/settings.json.
Restart Gemini CLI.
Inside the session, run `/mcp`.
Confirm `zephex` is listed as ready.

VERIFY

Confirm the MCP server is loaded before you rely on it in normal prompts.

Run `/mcp` inside a Gemini session.
You should see "zephex" listed with status "ready" or "connected".
Ask Gemini: "what tools are available from zephex?" You should see all 10 tools.

COMMON ISSUES

`zephex` does not appear in `/mcp`

Make sure you saved the file before starting Gemini CLI, then restart the session after editing the config.

Connection works but tools are missing

Check that the config uses `command`, `args`, and `env` exactly as shown above instead of the older hosted HTTP fields.

`npx` is not found

Install Node.js so `npx` is on PATH, or switch to absolute `node` and package paths if your environment does not inherit PATH correctly.

If the editor still does not connect, return to Quickstart or check Connection Issues.