MNEME
Why Mneme How it works Sign in
Get Mneme

Connect Mneme to Gemini CLI

You’ve been running Gemini CLI in the terminal and the project context vanishes the moment you close it. Mneme is the fix — same vault you’d use in Claude, available to gemini too. Three minutes to wire it up.

Sign in to Mneme

If you haven’t already, open mneme.tools and click Continue with Google. You’re in.

Copy the connector URL

In Mneme, open Settings from the side menu. Halfway down there’s a field labelled MCP Connector URL. The value is:

https://mneme.tools/mcp

Click the copy icon. That’s the link Gemini CLI needs.

Hand-drawn ink illustration of connecting Mneme to Gemini CLI. On the left, a Mneme settings card with the MCP Connector URL https://mneme.tools/mcp. A hand carries the URL pill toward a Gemini CLI config file labelled '~/.gemini/settings.json' showing an mcpServers block with mneme and a url field.
Same vault, different harness. Gemini CLI uses dynamic OAuth discovery — no client ID to wire by hand.

Add Mneme to your Gemini CLI config

Open ~/.gemini/settings.json. If it doesn’t exist yet, create it. Add an mcpServers block:

{
  "mcpServers": {
    "mneme": {
      "url": "https://mneme.tools/mcp",
      "authProviderType": "dynamic_discovery"
    }
  }
}

That’s the whole config. dynamic_discovery tells Gemini CLI to ask Mneme how OAuth works rather than hardcoding a client ID — which is what you want, because Mneme registers Gemini as a client on the fly.

If you already have other MCP servers in mcpServers, add mneme alongside them — don’t replace the block.

To scope this to one project instead of every Gemini CLI session, drop the same JSON into .gemini/settings.json inside that project’s folder.

Verify your email

Start gemini and ask it anything. The first time it tries to reach Mneme, the connection fails with a 401, Gemini CLI discovers the OAuth endpoints, and a browser tab opens automatically.

The page asks for your email and offers a Send sign-in link button. Type your email, click the button, then check your inbox.

Yes — even though you’re already signed in to Mneme on the web. Gemini CLI is a different door, and Mneme only opens doors with proof you can read your own email. It’s not retyping your login; it’s signing the lease for this terminal.

Click the link in the email and confirm.

If you see Your account is not authorized to access Mneme — Mneme is in early access and accounts are added by hand. Reply to the invite email and we’ll add you.

Pick what this Gemini can see

Mneme shows the Authorize access panel with two checkboxes:

  • Personal — Home, mobile, cowork — your full personal vault.
  • Work — Work-tagged docs only. Enable on work devices so personal data stays private.

Both are on by default.

If this is your personal laptop, leave them on and click Authorize. If this is a work machine, uncheck Personal first. (Why that matters →)

The browser tab closes. Gemini CLI is now connected and the OAuth tokens live in ~/.gemini/mcp-oauth-tokens.json — Gemini refreshes them itself when they expire.

Check it works

In your terminal, run:

gemini mcp list

You should see mneme with a connection status next to it. Then ask Gemini something only Mneme could answer:

what’s in my Mneme vault about the Q3 plan?

If it pulls a real excerpt, the wire is live. From here on, every gemini session — or every session in this project, if you scoped it locally — has Mneme as the memory layer behind it.

If you ever need to re-auth (rotated email, revoked token), use /mcp auth inside a Gemini session.

Tagged: , , , ,