This article explains how to connect Gemini to the R2 Docuo AI connector, so you can query your repository from Gemini.
This integration does not currently work in Gemini Enterprise, Business edition. The R2 Docuo server registers correctly, but Gemini does not get as far as listing its tools, so the connection looks complete while the assistant cannot query anything in the repository. The fault is on Google’s side and we have a ticket open with them. We are leaving the published steps unchanged, because this is not a configuration problem, and we will update this article as soon as Google resolves it.
Before you start, an administrator of your repository must have enabled the connector and granted you access. See Requirements and activation of the AI connector.
AI assistants change their menus and their capabilities frequently. The steps in this article describe the process in Gemini as of September 2026: an option may have moved, been renamed, or become unnecessary in your version. If something does not match, search for “MCP server” or “connected apps” in its own settings.
What you need
- An R2 Docuo account as a contracted user, with “MCP access” granted, and your password.
- Gemini Enterprise. Unlike other assistants, connecting MCP servers in Gemini is managed at team level rather than from a personal account, and requires team management permissions.
- The server address:
https://mcp.r2docuo.com
Google is rolling these capabilities out in phases and the menus change often. If your version of Gemini does not yet offer MCP server connections, the alternative is Gemini CLI, described at the end.
Requesting the client id and client secret
Most assistants register themselves with our authorisation server and need nothing configured. Gemini does not: its form will ask you for an OAuth client id and client secret.
We issue those credentials at the customer’s request. The request is raised by an administrator, because R2 Docuo support is limited to administrators and advanced users: if you are not one, ask whoever administers your repository to open the ticket.
- An administrator opens a support ticket from their R2 Docuo account.
- They state that they need fixed client credentials for the MCP server, which assistant they are for — Gemini, in this case — and which repository will be used.
- We send back a client id and a secret through that same channel.
There is no need to supply the return URL: Gemini sets it and the server accepts whatever it brings.
The client id and secret identify the assistant, not a person: they do not replace your authorisation. Each user still signs in with their R2 Docuo account and queries with their own permissions.
The client secret is a service access password. Configure it only in the system it was issued for, keep it safe, and do not enter it into third-party applications or services you do not control. If you suspect it has been compromised, request its rotation through a support ticket. We may also rotate or revoke credentials for security reasons, informing you as soon as possible.
Adding the MCP server
- Sign in to Gemini Enterprise.
- Open Settings and help and select your team.
- Go to Manage team and from there to Connected apps.
- Choose Add MCP server.
- Enter a recognisable name — R2 Docuo — and the server address:
https://mcp.r2docuo.com - Fill in the client id and client secret we sent you through the support ticket.
- Confirm. The R2 Docuo sign-in screen will open: enter your user name and password, choose the repository and accept the consent screen.
Your password is only ever typed into the R2 Docuo screen; Gemini neither sees nor stores it.
Authorisation is personal even though the server is registered at team level: each person signs in with their own R2 Docuo account and queries with their own permissions. The server being available to the team does not give anyone access to documents they could not already see in Docuo.
Checking that it works
Open a conversation and ask:
Which R2 Docuo repository are you connected to, and what can you do there?
It should answer with your user name, the repository identifier and a summary of what it can query. There are more examples in What you can ask the AI connector.
Alternative: Gemini CLI
If you work with Gemini’s command-line tool, MCP servers are declared in its configuration file, ~/.gemini/settings.json, adding the R2 Docuo server with its address. Check the Gemini CLI documentation for the current syntax, which evolves with the tool.
Disconnecting
In Manage team → Connected apps, remove the R2 Docuo MCP server.
From the Docuo side, an administrator can withdraw one person’s access at any time without touching Gemini’s configuration: that person’s next query will be rejected.
If something does not work
| What you see | What to check |
|---|---|
| The option to add an MCP server does not appear | That your edition of Gemini includes it and that you have team management permissions. If not, use Gemini CLI. |
| The form asks for a client id and secret | That is normal in Gemini. Request them through a support ticket, as explained above. |
| Invalid client error when authorising | That the client id and secret are copied correctly, without spaces, and that they have not been revoked or rotated. |
| You sign in but your repository does not appear | That the administrator has enabled the connector on that repository, or set your “MCP access” to “Allowed”. |
| The server is registered but it does not work for one person | That the person has a contracted user account on the repository and access granted. Collaborators cannot use the connector. |
| It used to work and has stopped | That access has not been withdrawn, that artificial intelligence has not been switched off on the repository, and that your plan’s usage limit has not run out. |
If the problem persists, open a support ticket stating the repository, the affected user and the approximate time of the attempt.