Gemini CLI

Gemini CLI integrations use the same scoped-key contract as other first-party agents. Gemini/Vertex is not the default UnifiedMemory cognition lane; MiniMax is the default UM-owned cognition provider, while Google Memory Bank remains a managed co-processor.

Registry contract

This section is generated from integrations/agent_integrations.registry.json. Edit the registry or generator, not this block.

Field	Value
Integration ID	gemini
Label	Gemini CLI
Tier	remote_mcp_client
Setup mode	http_mcp
Agent ID	gemini
App ID	gemini
Source app / actor	source_app=gemini, agent_id=gemini; key metadata wins over request body hints
Default scope	own
Config paths	~/.gemini/settings.json, .gemini/settings.json, GEMINI.md
Capabilities	memory.read, memory.write, memory.recall, memory.delete, agent.context, agent.writeback, mesh.read, evidence.read, courtroom.read, canary.read
Supported tools	geminiBootstrap, geminiCapture, geminiStatus, um_store, um_search, um_profile, um_courtroom

Capture policy

User-scoped HTTP MCP plus repo hooks for BeforeAgent/AfterAgent capture when configured.

Install command(s)

gemini mcp add --transport http --scope user -H "Authorization: Bearer {{KEY_REF}}" unified-memory {{MCP_URL}}

Verify command(s)

gemini mcp list

Environment

{
  "UNIFIED_MEMORY_API_KEY": "{{KEY_ENV_REF}}",
  "UNIFIED_MEMORY_CONTAINER": "{{CONTAINER_TAG}}",
  "UNIFIED_MEMORY_URL": "{{EDGE_BASE_URL}}"
}

Risk notes

• Keep tracked .gemini/settings.json hook-only.
• Use user scope for live MCP server credentials.

Official upstream docs

https://github.com/google-gemini/gemini-cli/blob/main/docs/tools/mcp-server.md

Scope and capabilities

Setting	Value
Source app	gemini
Default container	jeethendra
Default scope	own
MCP URL	https://edge-api.jithendranara.dev/mcp

Install

gemini mcp add --transport http --scope user \
  -H "Authorization: Bearer <scoped-key>" \
  unified-memory https://edge-api.jithendranara.dev/mcp

Verify

List MCP tools from Gemini CLI and run a small recall canary. The response should identify effective source app gemini and should not expose other agents' working memory.

Memory behavior

• Gemini may recall own working/session memory and approved canonical facts.
• Google Memory Bank output is comparison evidence, not automatic truth.
• MiniMax remains the default UnifiedMemory judge/cognition lane.

Risk notes

If Gemini tooling has its own memory layer, keep it separate from UnifiedMemory writeback unless the integration explicitly calls retain or writeback with a scoped key.