One click

Connect Clad9 to Gemini CLI

A block of JSON in your settings file. There is nowhere to paste a URL.

Before you start

Gemini CLI disables every MCP server — including the ones in your own settings file — in a folder it hasn't been told to trust. If clad9 shows as Disabled rather than Connected, that is why: trust the folder when the CLI offers, or start it with --skip-trust.

Step by step

Open ~/.gemini/settings.json. Create it if it isn't there.

Add this block. If the file already has an "mcpServers" object, put the "clad9" entry inside it rather than adding a second one.

{
  "mcpServers": {
    "clad9": {
      "httpUrl": "https://clad9.com/mcp",
      "authProviderType": "dynamic_discovery",
      "oauth": {
        "enabled": true
      }
    }
  }
}

Start Gemini CLI and run /mcp auth clad9. Your browser opens on a Clad9 screen listing what it is asking for; approve it and come back.
04
Check it from a terminal at any time.
```
gemini mcp list
```

You'll need a Clad9 account

The key is tied to your closet, so it can only be created from inside Clad9. Log in and come back to this page: the form appears right here.

This is the shape of what you'll paste:

{
  "mcpServers": {
    "clad9": {
      "httpUrl": "https://clad9.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CONNECTION_KEY"
      }
    }
  }
}

You'll know it worked when

gemini mcp list shows clad9 as Connected, and /mcp lists its tools. Ask “what's in my laundry basket?” to check it.

Nothing to answer from? An assistant can only use clothes Clad9 knows about, so catalogue your closet first. If it can't connect at all, that's ours to fix: tell us.

Using something else?

What an assistant can and can't do, including what it's never offered, whatever you tick.