How to Connect Notion to Gemini: Every Working Route
How-to — — by Mahmoud Zalt
Notion is not in the Gemini app's connected apps list. Here are the routes that do work, from the Gemini CLI to Gemini Enterprise, and what each costs.
This is the search where most people arrive expecting a toggle and leave slightly annoyed. It is worth saying the awkward part first, because half the guides online skip it and send you hunting through a settings screen for something that is not there.
The good news is that three real routes exist and all three work. They just serve different people. One is for someone comfortable editing a config file, one is for a company with an admin, and one is for everybody else.
Read the first section, decide which of the three you are, then skip to that one. The last section on limits applies to all of them and is the part worth not skipping.
Which route should I use?
If you are one person and do not mind a terminal, use the Gemini CLI with Notion's MCP server. If you are setting this up for a company, use Gemini Enterprise and build a Notion data store. If neither of those describes you, use an automation platform to move content between the two products instead.
| Route | Who it suits | What it needs | What you get |
|---|---|---|---|
| Gemini CLI plus Notion MCP | One person, comfortable in a terminal | A settings file edit and a browser sign in | Live read and write against your own workspace |
| Gemini Enterprise data store | A company with an admin | A public Notion OAuth integration and Google Cloud access | Notion content searchable inside Gemini Enterprise |
| Automation platform | Anyone, no code | An account on the platform and a Notion connection | Content moved on a trigger or a schedule |
| The Gemini app itself | Nobody, for now | Not applicable | Notion is not in the connected apps list |
How do I connect Notion to the Gemini CLI?
You add Notion's MCP server to the CLI's settings file, then sign in through your browser the first time it connects. Google's documentation covers three transports and the one you want here is HTTP streaming, configured with the httpUrl key inside an mcpServers block.
Settings live in one of two places. A file at the user level applies everywhere, and a project level file applies only inside that folder. Either works for this.
That is the whole configuration. There is no secret to paste, because Notion's server handles sign in through OAuth and the CLI discovers what it needs from the server's own responses. Google documents that the CLI detects an authentication requirement, opens a browser, and stores the resulting token for you.
Set up the CLI route
- Create or open the settings file — Google documents a user level file and a project level one. Start with the user level file if you want Notion available in every project.
- Add the server block — Use the httpUrl key with Notion's published address. Notion also documents an older event stream endpoint if your client cannot handle HTTP streaming.
- Start the CLI and let it sign you in — On first connection a browser window opens for the Notion authorization. Google notes that the callback goes to a local address, so this needs a real browser on the same machine.
- Check the workspace name on the approval screen — If you belong to a personal and a company workspace, approving the wrong one produces an assistant that insists your workspace is empty.
- Ask something you can verify — Name a page you have open and ask for its last line. A correct answer means the wiring works. Only then try a write.
One catch worth knowing before you start. Google's documentation is explicit that this sign in needs local browser access, so it will not complete over a plain remote shell session or inside a container without a browser. If you live on a server, plan for that.
How do I connect Notion to Gemini Enterprise?
You create a public OAuth integration in Notion, give Google's service the redirect addresses it expects, then build a Notion data store on the Google side using the client ID and secret. Google's own documentation walks both halves, and the Notion integration has to be public rather than internal.
Public sounds alarming and is not. Google's documentation notes that a public Notion integration is not visible or accessible outside your organisation unless you submit it for publishing, which you have no reason to do.
- In Notion, create a new integration and choose the public type, then fill in the organisation details it asks for.
- Add the two OAuth redirect addresses that Google's documentation specifies for its search service. Getting one character wrong here is the most common failure.
- Under content capabilities, enable reading content so the integration is allowed to fetch pages.
- Copy the OAuth client ID and secret from the integration settings.
- On the Google side, create the Notion data store and paste those credentials, then let the first sync run.
This route is the one to pick when several people need the same answers from the same workspace. It is also the one that needs an actual admin, since it touches both a Notion workspace and a Google Cloud project.
What about connecting them without any of that?
Use an automation platform. Make, n8n, Zapier and others all publish Notion and Gemini integrations, and they solve a different problem from the two routes above. Rather than letting Gemini reach into Notion during a conversation, they move content between the two on a trigger or a schedule.
That fits a surprising number of the jobs people actually want. Summarise every new row in a database. Draft a follow up when a status changes. Write the result back as a page. None of those need a live connector, and all of them need to happen when you are not watching.
This is also the point where the framing changes. Once the job runs on its own, you are no longer connecting a chat window to a database, you are hiring somebody to own an outcome. That is the shape we build at Sistava, where you connect the tools once and describe the work in plain English instead of drawing the wiring diagram yourself.
What can Gemini actually see in my Notion workspace?
On the CLI route, exactly what your own account can see. Notion's help centre states that these tools act with your full Notion permissions, so a colleague's private page stays invisible and a teamspace you were never added to stays invisible. Nothing about connecting widens your access.
On the Enterprise route the boundary is drawn by the integration rather than by you personally, which is why that setup involves an admin and a deliberate capability choice. Either way, the honest summary is the same: connected means reachable on request, not read and memorised.
That last point catches people out repeatedly. Nothing is indexed in advance on the CLI route, so a page with a vague title and no matching words can sit there for months without ever appearing in an answer. Your page titles are now part of the tooling.
What none of these routes will do
Every route here has a hard edge, and all of them are consequences of the design rather than faults you can configure away.
- None of them puts Notion in the Gemini app. Google's connected apps list is what it is, and it varies by device and country on top of that.
- The CLI route will not sign in without a browser on the same machine, which rules out plain remote sessions and browserless containers.
- No route reaches past Notion's permissions. When the answer lives in a page you cannot open, the fix is a sharing change, not a better prompt.
- Nothing here is built for sweeping a whole workspace. Notion documents an average of three API requests per second per user, so a pass over hundreds of pages is slow.
- A live connector does nothing while you are asleep. If the work must happen on a schedule, that is the automation route's job, not the connector's.
None of that makes any of these routes a bad choice. It makes them specific. Match the route to the person you are and the job you have, and all three behave well.
Frequently asked questions
FAQ
Why is Notion not in Gemini's connected apps?
Google's help pages list the connected apps available in the Gemini app, and that list is built around Workspace services such as Gmail, Drive, Docs, Calendar, Keep and Tasks plus a set of partner apps. Notion is not on it at the time of writing. Google also notes the list varies by app, device and country, so what a colleague sees is not proof of what you will see.
Can Gemini write to Notion, or only read?
Through the MCP route it can do both, because Notion publishes tools for creating pages and updating page properties alongside search and fetch. Whether a specific write succeeds depends on the access level your account holds on that page. On the Gemini Enterprise route the capability you enable during setup is reading content, which is a read oriented connection by design.
Do I need Google Cloud for this?
Only for the Gemini Enterprise route, which is a Google Cloud product and involves creating a data store there. The CLI route needs no cloud project at all, just the settings file and a browser sign in. The automation route needs neither, only an account on whichever platform you choose.
Is the public Notion integration a security problem?
Public in this context describes the integration type rather than its visibility. Google's documentation states that a public Notion integration is not visible or accessible outside your organisation unless you submit it for publishing. The thing worth being careful about is the client secret, which should be treated like any other credential and never pasted into a shared document.
Why does my terminal sign in never complete?
Almost always because there is no usable browser where the CLI is running. Google documents that the authorization redirect goes to a local address on the same machine, so a session over a plain remote shell or a container without a browser cannot finish the flow. Run it locally once to create the stored token, or use a route that does not need interactive sign in.
Can I use the same setup for a whole team?
The CLI route is personal by design, since it carries the permissions of whoever signed in, and Notion describes this style of connection as suited to single player use. For shared team access to the same knowledge, the Gemini Enterprise data store is the route built for it, which is also why it requires an admin rather than an afternoon.
Sources
- Google, Use and manage connected apps in Gemini for the connected apps list and the note that it varies by app, device and country.
- Google, Gemini CLI MCP server configuration for the settings file locations, the transport keys and the browser based OAuth flow.
- Google Cloud, Notion configuration for Gemini Enterprise for the public integration requirement, the redirect addresses and the read content capability.
- Notion Docs, Connect to Notion MCP for the server address and the alternative event stream endpoint.
- Notion Help Center, Connect AI tools with Notion MCP for the permissions statement and the single player note.
- Notion Docs, Request limits for the average of three requests per second.
Pick one route, set it up, and test it with a question you already know the answer to before you trust it with a real one. That single habit catches the wrong workspace, the missing permission and the badly titled page in about two minutes each. Then ask yourself the harder question, which is whether you want to be the person driving this at all. If the honest answer is no, the setup you want is not a connector but a hire, and you can start one on Sistava.