layven.
Sign in

Connect Gemini

Add Layven to the Gemini CLI settings file with an agent token. Use httpUrl, not url, or it will not connect.

Last updated 4 August 2026

This takes about two minutes. Gemini CLI has no browser approval flow, so you create an agent token in the console and paste it into a settings file once.

Before you start: you need a Layven account with at least one workspace. If you have not made one yet, create your drive first.

  1. Create an agent token

    In the Layven console, open Agents and create a token. Scope it to the workspace you want Gemini to reach, then copy the secret. It is shown once.

  2. Add Layven to your Gemini settings

    Open ~/.gemini/settings.json and add this block, replacing the token with the one you just copied.

    ~/.gemini/settings.json
    {
  "mcpServers": {
    "layven": {
      "httpUrl": "https://api.layven.io/mcp",
      "headers": {
        "Authorization": "Bearer agd_your_agent_token"
      }
    }
  }
}
    Careful: the key must be httpUrl, not url. Gemini CLI reads url as an older SSE transport, and Layven only serves Streamable HTTP, so the connection will not establish at all with the wrong key.
    Careful: do not commit this file with your token in it. Give any teammate their own token instead of sharing yours.

  3. Restart Gemini CLI

    Restart the CLI, or run /mcp inside a session to refresh its server list. Layven should show up as connected.

  4. Write a test file to confirm it worked

    Ask Gemini to create a file:

    Write a file called hello.md in my Layven workspace that says hello from Gemini.

    Open the Layven console and look for hello.md at version 1, attributed to the token you created. If it is there, the connection works, and any other agent you connect reads that same file without you copying anything anywhere. You are done.

Revoke access

Open Agents in the console and revoke the token. It stops working on the next request, and everything Gemini wrote stays exactly where it is with its history intact.

Next

Connect a second client and point it at the same workspace. Two agents sharing one drive is the part that does not exist anywhere else: Claude, Cursor, or Claude Code.

← All guides