Lovie MCP›Gemini CLI

Terminal

Gemini CLI

Gemini CLI handles the whole OAuth dance for you and caches the tokens on disk. Its settings key for a streamable-HTTP server is httpUrl — a plain url is silently the wrong field.

The only value you need

• Time 1 minute
• Transport HTTP streamable
• Auth OAuth — /mcp auth
• Key httpUrl

Add the server

Sign in

1. Start a Gemini CLI session.
2. Run /mcp auth to see which servers still need authorization.
3. Run /mcp auth lovie. Your browser opens the Lovie sign-in.
4. Approve. The CLI stores the token at ~/.gemini/mcp-oauth-tokens.json and refreshes it on its own from then on.
5. Run /mcp to confirm the server is connected and see its tools.

Or write settings.json

Scope	File
Every project	~/.gemini/settings.json
This project	.gemini/settings.json

{
  "mcpServers": {
    "lovie": {
      "httpUrl": "https://mcp.lovie.co/mcp",
      "authProviderType": "dynamic_discovery"
    }
  }
}

Check it worked

> /mcp
> using lovie, list my companies

If something goes wrong

Symptom	Cause
Server present, zero tools	You used url instead of httpUrl, so the transport never came up.
/mcp auth lists nothing	The server is already authorized, or it is not configured in this scope. Check /mcp.
Authorized, then refused again later	Delete the entry from ~/.gemini/mcp-oauth-tokens.json and run /mcp auth lovie once more.

Somewhere else