Gemini
The Gemini app accepts any standards-compliant MCP server as a custom Connected App for Gemini Spark. You paste the URL, approve the connection, and Engram’s tools become available to Spark on both web and mobile. Engram supports dynamic client registration, so there are no credentials to create. For protocol background, see MCP.
Prerequisites
Section titled “Prerequisites”Before you start, confirm:
- You have an Engram account at app.engram.page.
- At least one vault is synced. Open the Obsidian plugin or the web app and confirm notes have synced within the last day.
- You can sign in via browser. The MCP auth flow opens a browser window.
Plus the Gemini-specific requirements in the box above.
Endpoint
Section titled “Endpoint”https://mcp.engram.page1. Open Connected Apps. Go to gemini.google.com, then Settings & help → Connected Apps. On some accounts it sits one level deeper, under Personal Intelligence → Connected Apps. You can also go straight to gemini.google.com/apps.
2. Add the app. Under Custom apps for Spark, use the Add a custom app link to get started field, or click Add a custom app if you have connected one before. Paste the endpoint:
https://mcp.engram.page3. Continue. Click Next and follow the prompts. Leave Advanced features alone: that section is for servers without dynamic client registration, and Engram has it, so Gemini negotiates the connection on its own.
First-run auth
Section titled “First-run auth”Because Engram advertises OAuth 2.1 with dynamic client registration,
Gemini registers itself and runs the consent flow inline. Sign in to
Engram, approve the connection, and the app is linked to your Google
Account. There is no client ID, secret, or API key to paste. The grant
is the full mcp scope. Granular per-action
scopes are on the roadmap.
Gemini asks you to confirm every write action a custom app
performs. Treat that prompt as the real safety boundary, since the
mcp grant itself covers writes and deletes.
Tell Gemini how to use it
Section titled “Tell Gemini how to use it”Add the snippet below to Settings → Saved info, Gemini’s persistent personalization field. It applies across conversations.
Engram holds my personal notes — treat it as your long-term memory of me. Search it when a question depends on context I might have shared before. Before saving or updating a note, ask first.Try it
Section titled “Try it”In Gemini Spark, ask:
- Search my vault for notes about the engineering interview process and summarize the top three.
- Find anything I wrote about embeddings in the last month.
If Gemini answers from general knowledge instead of reaching for your
vault, name the app explicitly: type @ and select Engram from the
list. That pins the request to the connected app.
Gemini CLI users
Section titled “Gemini CLI users”Gemini CLI had its own MCP client, but Google retired it on
2026-06-18. It stopped serving Google AI Pro, Ultra, and free-tier
requests on that date, and those tiers moved to Antigravity CLI. If
you were using Engram through ~/.gemini/settings.json, see
Antigravity instead, which covers
both the CLI and the desktop app.
Privacy note
Section titled “Privacy note”Engram is a private notes vault, so two things on this path deserve a second look before you connect.
Keep Activity must be on. This connector will not work with Google activity retention disabled. If you keep that setting off deliberately, this integration is not for you, and the Obsidian plugin or web app reach the same vault without the tradeoff.
Google states plainly that it does not control, monitor, or secure third-party MCP servers. That cuts both ways here: it is a general warning to Gemini users about arbitrary servers, and it is a fair description of the boundary. Once Gemini calls Engram, your note content is handled under Engram’s terms, not Google’s.
Troubleshooting (Gemini specific)
Section titled “Troubleshooting (Gemini specific)”- No “Custom apps for Spark” section. You do not have Spark access, or you are signed in with a work or school account. Check which account is active first; the section is absent rather than disabled for ineligible accounts.
- “Connected Apps” is missing from settings. Look under Personal Intelligence first. The menu position varies by account.
- The connect flow refuses to finish. Confirm Keep Activity is on and that the app language is English. Both are hard requirements, and neither failure names itself clearly.
- Connected on desktop but absent on mobile. Custom apps are added on web only, then sync. Reopen the mobile app; if it stays missing, confirm the same personal Google Account is signed in on both.
- Gemini answers without touching your notes. Pin the app with an
@mention, or add the Saved info snippet above so it reaches for Engram by default.
For cross-client failures, see Troubleshooting.
Revocation
Section titled “Revocation”To disconnect Gemini from Engram:
- In Gemini, find the connector or MCP server entry and remove it.
- In Engram, open your account → API Keys & Sessions and revoke the matching session.
- The OAuth token is invalidated server-side. Gemini will need to re-authenticate to reconnect.
Google splits this into three different actions, which are easy to confuse:
- Disconnect (toggle it off under Custom apps for Spark) stops Gemini using it, but keeps the entry.
- More details → Disconnect unlinks the MCP server from your Google Account and revokes its permissions, keeping the entry so you can relink later.
- More details → Remove app deletes the entry and unlinks the server.
You can also unlink from your Google Account’s Linked apps page. Revoke the matching session in Engram as well; unlinking on Google’s side alone does not invalidate the token server-side.