Gemini CLI

Connect

1. Add Soil to ~/.gemini/settings.json · httpUrl is Gemini CLI's key for a remote streamable-HTTP server:

   {
     "mcpServers": {
       "soil": {
         "httpUrl": "https://mcp.nativesoil.dev/mcp/soil"
       }
     }
   }

   If the file already has an mcpServers object, add the "soil" entry to it.

2. Gemini CLI handles the OAuth sign-in flow itself: it detects that Soil requires authentication and opens your browser. Sign in with Google, or with email and password. You don't supply a client id or secret; the client registers itself automatically (Soil's OAuth bridge implements Dynamic Client Registration). If the sign-in prompt doesn't appear, run /mcp auth soil inside Gemini CLI.

3. Open a Gemini CLI session where you've done real work and type soil save. (If you just want to confirm the connection, soil info does that, but the real proof is a save you can load back.)

Use Soil

The commands are the same in every client · same grammar, same account. You type them in plain language in the conversation; the model calls the matching Soil tool. @ says where, # says which:

soil save                       save this conversation as a graded handover
soil save #my-name              save under your own name · kept, never overwritten
soil save #my-name @project     add to a shared project · either order
soil list                       your handovers · soil list @project for a team
soil load #001                  load by exact code · by name: soil load #my-thread
soil load @project              whole-project restore · #NNN or #name for one thread
soil info                       your account status · the connection check

Save in this client, load in any other. See the soil commands for details and the reference for every form.