Agents

Uteke for Gemini CLI

Google · Coding agent · MCP + API key · Beta

The Gemini agent in your terminal.

Beta: written from Gemini CLI's own documentation and not tested by us yet. If a step does not match what you see, follow Gemini CLI's docs and tell us at [email protected].

Set it up

  1. Create an API key at API keys in the Uteke portal.
  2. Add Uteke to your settings. Gemini CLI needs httpUrl (url means the older SSE transport):
    ~/.gemini/settings.json 
    {
  "mcpServers": {
    "uteke": {
      "httpUrl": "https://uteke.app/mcp",
      "headers": { "Authorization": "Bearer utk_live_YOUR_KEY" }
    }
  }
}

  3. Start Gemini CLI and run /mcp to check that uteke is connected.

API keys are made at API keys in the portal; choose read-only if the agent only needs to recall. A key works only for your workspace.

Uteke's sign-in registers clients through their published client metadata (CIMD); this client's docs describe a different registration, so use an API key.

Try it

Ask Gemini CLI:

  • Remember that we release from main only, never from develop.
  • What did we decide about pricing last week?
  • Save this summary to the team room.

Then ask the same thing from another agent you connected: they share one memory.

Disconnect

Open Agents in the portal and choose Disconnect. It works for agents that signed in and for API keys; access is checked again within about 30 seconds. You can also remove Uteke in Gemini CLI's own settings.

Gemini CLI's documentation on MCP servers: https://geminicli.com/docs/tools/mcp-server/

Other agents: see all agents or the general steps.