How does authorizing Tempreon work in Gemini CLI?

After adding the server, start Gemini CLI and run /mcp auth tempreon. A browser tab opens to Tempreon's consent screen, where you sign in to your Tempreon account and approve. The tokens are then stored locally in ~/.gemini/mcp-oauth-tokens.json. If you later see Unauthorized or stale-token errors, run /mcp auth tempreon again to re-authorize.

Where do I add the Tempreon server in Gemini CLI, and which config field do I use?

The fastest way is one command: gemini mcp add --transport http tempreon followed by the Tempreon URL and -s user, which writes the entry to your user-level ~/.gemini/settings.json so it is available in every project. You can instead edit that file by hand and add Tempreon under an mcpServers block, using url with "type": "http". The Gemini Code Assist VS Code extension reads the same settings file.

Should my Tempreon entry use url or httpUrl in Gemini CLI?

Use url with "type": "http", which is what gemini mcp add --transport http writes for you. That selects Streamable HTTP, the transport Tempreon uses. An older httpUrl entry still works, but Gemini CLI now marks it as deprecated and prints a warning, so it is worth migrating. A url with no type also tries Streamable HTTP first. Then run /mcp auth tempreon to complete authorization.

Gemini CLI Setup — Docs

Overview

Gemini CLI is Google's open-source terminal agent for Gemini models. It supports remote MCP servers with OAuth, so it can connect to Tempreon with a single command or a small settings.json entry.

Connecting Tempreon gives your terminal sessions persistent intelligence: your AI loads your Core Imprint, searches your Knowledge Vault for context, and remembers what it learns — and that memory is shared with every other tool you've connected.

Quick path: gemini mcp add --transport http tempreon <URL> -s user → /mcp auth tempreon → approve in the browser.

Availability (as of October 2026): On June 18, 2026, Gemini CLI stopped serving requests for consumer Google accounts — free, Google AI Pro, and Ultra. It continues to work with a Gemini API key (including Gemini Enterprise Agent Platform keys) and with existing Gemini Code Assist Standard or Enterprise licenses. Google stopped selling new Standard and Enterprise subscriptions after October 9, 2026; annual renewals and additional licenses end January 31, 2027, and monthly renewals end December 31, 2027. If you're setting up fresh, use a Gemini API key. Google has announced that Antigravity CLI is the path forward for consumers, but has not announced an end-of-life date for Gemini CLI on those API-key and enterprise routes, and it is still shipping releases. If you're on a consumer account, use Google Antigravity instead — it's Google's consumer replacement and has its own guide.

Note that Google's own gemini-cli README still advertises a free tier for personal Google accounts. That line predates the June 18 change — the announcement supersedes it.

Prerequisites

Gemini CLI installed, running against an account it still serves: a Gemini API key, or an existing Gemini Code Assist Standard or Enterprise license (see the availability note above)
A Tempreon account with at least one available Bridge slot
A browser for the authorization step

Step-by-Step Setup

1. Add the server

The fastest path is one command:

gemini mcp add --transport http tempreon https://api.tempreon.com/functions/v1/tempreon-mcp/mcp -s user

-s user writes the entry to your user-level ~/.gemini/settings.json, so it's available in every project. Include it deliberately — without -s, Gemini CLI defaults to project scope and the entry only applies to the directory you ran it in.

Prefer editing the file directly? Add this to ~/.gemini/settings.json (or a project's .gemini/settings.json for one workspace):

{
  "mcpServers": {
    "tempreon": {
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp",
      "type": "http",
      "oauth": { "enabled": true }
    }
  }
}

Use url with "type": "http". That selects Streamable HTTP, the transport Tempreon uses, and it's exactly what gemini mcp add --transport http writes. Older entries that use httpUrl still work, but Gemini CLI now treats that field as deprecated and prints a warning. Gemini CLI's own MCP docs page still describes the older behaviour, where url meant SSE; the code has moved on. The "oauth": {"enabled": true} block is optional, but it makes the auth expectation explicit.

The URL is also shown in your Bridges dashboard.

2. Authorize the connection

Start Gemini CLI and run:

/mcp auth tempreon

A browser tab opens to Tempreon's consent screen — sign in to your Tempreon account and approve. Tokens are stored in ~/.gemini/mcp-oauth-tokens.json.

3. Verify it's working

Run /mcp to check server status, or ask "What Tempreon tools do you have access to?" — if it answers with a list, the Bridge is live.

Gemini Code Assist

The Gemini Code Assist VS Code extension's agent mode reads the same ~/.gemini/settings.json, so the config above carries over with no extra steps. If the OAuth flow doesn't complete inside the IDE, run the authorization once in Gemini CLI (/mcp auth tempreon) — settings and tokens are shared, so the IDE picks up the authenticated server.

Troubleshooting

Requests aren't served on a personal Google account. That's the June 18, 2026 consumer retirement, not a Tempreon problem — some third-party guides (and Google's own CLI README) still describe the free tier, but that information is out of date. Use Google Antigravity instead.

Moving to Antigravity CLI? Antigravity's CLI (the agy command) reads a different file — ~/.gemini/config/mcp_config.json — and uses the serverUrl field rather than url, so the entry above doesn't carry over as-is. Antigravity offers to migrate legacy config on first launch — that onboarding pass is what picks up a Tempreon entry added with gemini mcp add, since it covers global configurations. agy plugin import gemini works from your legacy extension manifests, converting extensions into plugins, commands into skills, and MCP server definitions into mcp_config.json entries. Verify the result, and see the Antigravity guide for the field names.

Connection fails immediately. Confirm the URL ends in /mcp with no trailing slash: https://api.tempreon.com/functions/v1/tempreon-mcp/mcp.

A deprecation warning mentions httpUrl. Your entry predates the current format. It still works, but to silence the warning, change "httpUrl" to "url" and add "type": "http", as in the example above.

The logs say "attempting SSE fallback". That means the Streamable HTTP connection failed and Gemini CLI tried SSE instead, which happens when the entry has a url but no type. Check that the URL ends in /mcp with no trailing slash, and add "type": "http" so Gemini CLI stays on Streamable HTTP. Then run /mcp auth tempreon.

"Unauthorized" or stale-token errors. Run /mcp auth tempreon again to re-authorize. Tokens live in ~/.gemini/mcp-oauth-tokens.json.

OAuth won't complete inside VS Code. Run the auth once in Gemini CLI — the shared settings mean the extension inherits the authenticated connection.

Also connect: Google Antigravity · Gemini App · Any MCP Client

Try saying...

"Start my session." — triggers session_start to load your Core Imprint
"Search my knowledge base for [topic] before we plan this change." — pulls your Knowledge Vault into the session
"Remember that [decision] — we chose it because [reason]." — stores the insight for every future session, in every connected tool