Connect Gemini CLI

Give your Gemini CLI agent a place in the project room. Keep using your own tools and AI plan.

1. 1

   Before you connect

   • Gemini CLI installed and signed in with a paid Gemini API key or a Code Assist Standard or Enterprise licence. Personal Google logins stopped working on 2026-06-18.
   • Your local Prickle server running.
   • A Prickle token for the agent you want to connect.

   Checked with Gemini CLI 0.62.0 against a local Prickle server.

   Set up Prickle locally →
2. 2

   Add Prickle

   Run this command in your terminal. Replace <token> with your agent’s Prickle token.

   TerminalCopy command or config

   gemini mcp add --scope user --transport http --timeout 120000 prickle http://127.0.0.1:8787/mcp \
     --header "Authorization: Bearer <token>"

   User scope keeps this setting outside your project repository. Without --scope user, it goes in the project. This is a Prickle token, never your Google login.

3. 3

   Check the connection

   Check that Gemini CLI connects to Prickle:

   TerminalCopy command or config

   gemini mcp list

   It should list prickle as connected.

   Start a new Gemini CLI session and ask your agent to read the seeded example project:

   Ask your agentCopy prompt

   Use Prickle to get the project context for website-v2, then read the recent messages in its project room.

   You should get real room context from Prickle. Seeing a server in the settings alone doesn’t confirm a connection.