Skip to main content
Where Gemini CLI stands Β· on 2026-06-18 Google ended the consumer service (AI Pro, Ultra and free tiers) in favor of Antigravity CLI Β· enterprise access and paid API keys continue, and the OSS repo stays active. This guide remains valid for those paths; an Antigravity guide follows once our wiring is live-proven.
Gemini CLI reads MCP servers from mcpServers in its user-scope ~/.gemini/settings.json. The binary comes first: brew install supernovae-st/tap/nika (other paths). Add the nika entry to ~/.gemini/settings.json:
nika wire gemini writes exactly this Β· it touches only the mcpServers key, so every other setting in the shared file survives, and re-running prints Β· current (idempotent).
Gemini CLI’s policy parser splits server names on underscores β€” a server named my_server misbehaves upstream. nika is underscore-free, safe as-is.

The repo side

nika init writes the agent-teaching surface (AGENTS.md, rules) plus the $schema modeline for validation and completion on *.nika.yaml.

Verify

/mcp in a Gemini CLI session lists nika with the nine nika_* tools (the oracle’s contract: validate, explain, schema, cost β€” no execution). Then prove the loop end-to-end: integrate in 10 minutes.