Connect Gemini CLI

Not yet tested. We haven't walked through these steps in Gemini CLI ourselves yet, so a menu or button may be named differently. If something doesn't match, tell us at support@flamap.app.

Before you start

A FlaMap account, and access to its email inbox.
Gemini CLI installed and signed in.
A browser on the same machine, for the sign-in page.

One line

gemini mcp add --transport http flamap https://api.flamap.app/mcp

Or add it to ~/.gemini/settings.json yourself. Use httpUrl, not url: url means the older SSE transport, which FlaMap does not serve.

{
  "mcpServers": {
    "flamap": {
      "httpUrl": "https://api.flamap.app/mcp"
    }
  }
}

If the file already has an mcpServers block, add only the "flamap": { … } entry inside it.

Steps

Run the one-liner above.
Start Gemini CLI: gemini.
Type /mcp auth flamap. A page on flamap.app opens in your browser.
Sign in to FlaMap (Google or an emailed code).
Read what Gemini CLI is asking for and where your data goes. Tick the consent box (Approve stays greyed out until you do), then select Approve.
Go back to the terminal.

Gemini CLI keeps the sign-in in ~/.gemini/mcp-oauth-tokens.json and renews it on its own.

Check that it works

Type /mcp list. flamap should be connected, with its tools listed.
Ask: "Using flamap, what is my FTP?"

Gemini CLI asks before it runs each tool. The answer should show your FTP and your estimated FTP over recent months.

Your first real question

"Using flamap, how many kilometres and metres of climbing did I ride each month this year?"

Disconnect

In Gemini CLI:

gemini mcp remove flamap

Add --scope user if FlaMap is in your user settings. The stored sign-in is in ~/.gemini/mcp-oauth-tokens.json.

In FlaMap: open flamap.app/settings/ai-assistants and revoke Gemini CLI. See the privacy page.

If something goes wrong

flamap shows as disconnected: run /mcp auth flamap again.
"SSE" errors: your settings use url; change it to httpUrl.
More in the README troubleshooting.