The R2 Docuo AI connector — its MCP Server — is switched off out of the box. This article explains what is needed to use it and how to enable it. It is aimed at repository administrators; if what you want is to connect your assistant, start with The R2 Docuo AI connector.
Enabling the connector means opening a new route into the repository from outside. That is why it starts switched off and only a user with administration privileges can enable it. It is not switched on by an update.
The four requirements
For someone to connect their assistant to a repository, four conditions must hold at once. They are checked on every query, not just when authorising: if any of them stops being met, access already granted stops working immediately.
1. A compatible plan
The connector is available on R2 Docuo’s current plans: One App, All Apps and Custom (the former Enterprise edition). The legacy Professional Edition and Business Edition plans do not include it.
The plans that include it at any given time, and the usage limits of each, are published on the pricing page.
2. Artificial intelligence, enabled on the repository
The connector hangs off the repository’s general artificial intelligence switch. If AI is switched off, the connector does not work, even if its own box is ticked.
Switching AI off does not untick the connector’s box: it disables it and keeps its value, so that switching AI back on leaves the connector as you left it.
3. MCP access, allowed for that user
Every user has an “MCP access” field on their record with three values, and this field overrides the repository setting:
| Value | What it does |
|---|---|
| Allowed | The user gets in even if the connector is disabled on the repository. |
| Disabled | The user does not get in even if the connector is enabled on the repository. |
| According to global configuration | The repository setting decides. This is the factory value. |
This lets you open the connector to one person without opening it to the whole repository, which is the recommended way to start: set it to “Allowed” for whoever is going to use it and leave the repository setting as it is.
As a consequence, a repository with the connector disabled may still have users getting in if someone set them to “Allowed” on their record. If you need to close the door to everyone, review the user records too.
4. Being a contracted user, not a collaborator
Collaborators have no access to the connector, and there is no way to grant it. A collaborator is a third party with restricted visibility, and the connector is a route reserved for the repository’s contracted users.
How to enable the connector
You need administration privileges on the repository. Enabling is per repository: if you manage several, you will need to repeat it on each one.
- Open the repository settings and go to the Artificial Intelligence tab.
- Check that the general artificial intelligence switch is on. Two sections hang off it: the R2AI Assistant and the MCP server.
- In the MCP section, tick publication of the repository through the MCP server.
- Save your changes.
The switch is also in the scripting IDE, on the toolbar of the MCP server tab, for anyone who normally works from there. It is the same setting in both places.
Granting access to a person
- Open the user record.
- Find the “MCP access” field, just below the two-factor authentication one.
- Choose “Allowed” and save.
That person can now connect their assistant by following the article for the tool they use.
Assistants that need client credentials
Most assistants register themselves with our authorisation server and only need the server address. Others cannot do that and ask for an OAuth client id and client secret: today this is the case for Gemini and Copilot.
We issue those credentials at the customer’s request, through a support ticket, and the request is raised by an administrator. When opening it, state which assistant they are for and which repository will be used. There is no need to supply the return URL: the assistant sets it and the server accepts whatever it brings.
- They identify the assistant, not a person. They do not replace the named authorisation: each user still signs in with their own account and queries with their own permissions.
- They are service access passwords. Configure them only in the system they were issued for, keep them safe, and do not enter them into third-party applications or services you do not control.
- They are rotated if there is any suspicion of compromise, at your request through a support ticket. We may also rotate or revoke them for security reasons, informing you as soon as possible.
The specific steps are in each assistant’s article: Gemini and Copilot.
How to withdraw access
You have three ways, from the most surgical to the most sweeping:
- From one person: set “MCP access” to “Disabled” on their record.
- From the whole repository: untick MCP publication on the Artificial Intelligence tab. Remember to review any user records set to “Allowed”, because that value prevails.
- All AI at once: switch off the general artificial intelligence switch. It disables the R2AI Assistant, the Artificial Intelligence Instructions and the connector, immediately.
Withdrawing access also cuts off access already granted. The next query the assistant attempts will be rejected, without the person having to do anything in their client. There is nothing to wait for it to expire.
What to weigh up before enabling it
The decision to enable the connector, and on which repositories, is yours. Three things worth thinking about first:
- The nature of the content. When answering, content leaves R2 Docuo towards the assistant each person has connected, and there it is governed by that provider’s terms. Weigh up whether that is acceptable for what you keep in that repository.
- Files from outside sources. If the repository receives documents from third parties, bear in mind that a file may contain text written so that a model reads it as an instruction.
- Workflows with automations. The connector can move a document between states. If a transition is configured to run an action automatically — a signature with your digital certificate, a certified electronic delivery — that action will run just the same when the transition is requested from an assistant. The connector does not use your certificate itself, but it can trigger an automation that does, with effects on third parties and consumption of Credits.
It is also worth making sure that whoever is going to use the connector knows its limitations: that answers must be reviewed, that models are not deterministic, and that what they return has no evidential value. The article The R2 Docuo AI connector is written for that and works as training material.
References
- Terms and Conditions of Service: clause 16.2 (R2 Docuo MCP Server), clause 16.3 (oAuth authorisation and credentials) and clause 21.i (activation and deactivation).
- Plans and pricing.
- Privacy Policy.