Gemini CLI's setup is two commands, plus one small config detail that is worth getting right the first time instead of debugging later.

Connect it

Add the server:

gemini mcp add --transport http develosaur https://mcp.develosaur.com/v1/user/mcp

Then, inside Gemini CLI, sign in:

/mcp auth develosaur

Or add it to settings.json directly

{
  "mcpServers": {
    "develosaur": {
      "httpUrl": "https://mcp.develosaur.com/v1/user/mcp"
    }
  }
}

The field name matters here. Gemini CLI uses httpUrl for a Streamable HTTP server like this one. Writing url instead, the key most other clients expect, makes Gemini CLI try the older SSE transport, which will not connect. One field name is the entire difference between it working and not.

If the sign-in itself gets stuck

A sign-in page that loops back usually means the email link opened in a different browser than the one that started the request; finish it in the same one. A corporate proxy or VPN blocking the callback typically clears on a retry off that network.

Full setup, troubleshooting and FAQ live on the Gemini CLI integration page. The sign-in is the same OAuth-only flow covered in why Develosaur has no API keys to paste; more of these are on the blog.