Skip to content

Integrations

Let an assistant read your rooms,without handing it the keys.

Connect Claude, Claude Code or any MCP client to the data rooms you choose, on Business and Enterprise. It reads what you allow, writes only if you say so, and cannot delete or rename anything at all.

Plans
Business, Enterprise
Default
Read only
Rooms
Off until you say
Revoke
Any time

AI assistant access is rolling out to Business and Enterprise accounts. If the connection step does not find the server yet, it has not reached your account.

What it can do

A small, deliberate set of tools.

An assistant does not get a general connection to your account. It gets a fixed list of named tools, and that list is the whole surface. Everything absent from it is absent because it was left out on purpose.

Read

list_datarooms
The data rooms you can reach whose owner is on Business or Enterprise.
list_documents
The documents inside a room you have shared with it.
read_document
The contents of a single document.
get_storage_usage
How much of your storage allowance is used.

Write, only if you grant it

create_text_document
Create a new markdown or HTML document in a room.
update_text_document
Update one it has already read, checking it has not changed underneath.
upload_document
Upload a file into a room.

By design, it cannot

  • Delete a document, a room, or anything else
  • Rename, move or archive anything
  • Change who a room is shared with, or issue a link
  • Answer a question in the Q&A in your name
  • Reach a room you did not choose at the moment you connected

These are not permissions held back at runtime. There is no tool for any of them, so there is nothing for a confused or manipulated assistant to call.

Before it works

Four gates, and three of them fail quietly.

Wrong plan, an organisation veto, and a room left switched off all look identical from the assistant's side: it connects, reports success, and sees nothing. Work through these in order and that whole class of confusion disappears.

  1. Be on Business or Enterprise

    Room access for assistants is a Business and Enterprise capability. The plan that counts is the plan of the room's OWNER, not of whoever connects the assistant.

  2. If you are in an organisation, check it is not switched off company-wide

    An organisation owner can forbid AI assistant access for everybody. That veto overrides every individual room switch, and it applies to rooms that were already switched on.

  3. Switch AI access on for each room

    Every room is off by default, including rooms you create after connecting. This is the step people miss: a connection can be perfectly healthy and still see nothing, because no room has been switched on.

  4. Connect, and choose the rooms at that moment

    The rooms you tick during the connect flow are fixed for the life of that connection. Widening it later means connecting again; that is deliberate, so a connection cannot quietly grow.

How to connect

Three ways in, same consent screen.

Whichever client you use, the approval happens on our side: you confirm it is you, then tick the rooms it may reach. Nothing is shared before that screen.

Add it as a custom connector, then approve it once.

  1. Open Settings, then Connectors, then Add custom connector.
  2. Paste the server URL: https://mcp.99datarooms.com/authed-mcp
  3. Sign in with the email on your 99 Data Rooms account and enter the code we send you.
  4. Tick the rooms this assistant may reach, and confirm.

One command, then approve it in the browser tab it opens.

  1. Run: claude mcp add --transport http 99dr https://mcp.99datarooms.com/authed-mcp
  2. Run /mcp and choose to authenticate.
  3. Finish the same email step and room choice in the browser.
  4. Check it worked with /mcp: the server should list as connected.

Standard OAuth 2.1. Nothing about this server is bespoke.

  1. Point the client at https://mcp.99datarooms.com/authed-mcp. It advertises its own authorization server and protected-resource metadata, so a compliant client needs no further configuration.
  2. Client registration is dynamic and open, so there is no key to request from us first.
  3. PKCE with S256 is required. A request without it is refused.
  4. Ask for datarooms.read, datarooms.write, or both. An unrecognised scope is refused outright rather than quietly dropped, so a client can never believe it holds a permission it was not granted.
datarooms.read Read
List rooms, list the documents in them, read a document, and see storage usage.
datarooms.write Write
Create and update native text documents, and upload a file. Granted separately from read.

Worth knowing first

Where your documents actually go.

An assistant sends the contents of the rooms you give it to your own AI provider, under your agreement with them, not ours. A zero data retention agreement you hold may not cover this route: Anthropic, for one, states that data processed by third-party tools or MCP servers is not covered by ZDR. If retention matters to you, check with your provider before you connect one.

We also make no claim to prevent prompt injection. An assistant reading a document that contains instructions may follow them, which is why the tool surface above is as small as it is and why nothing in it can destroy anything. See our security page for how we think about that.

Questions

The ones people actually ask.

Can an AI assistant delete or change my documents?

It cannot delete, rename, move or archive anything - no such tool exists for it to call. It can only write if you grant write access separately, and even then it creates and updates documents rather than removing them.

Which rooms can it see?

Only the rooms you tick at the moment you connect it, and only if those rooms have AI access switched on. Every room is off by default. The set is fixed for the life of that connection, so it cannot quietly widen later.

Does my data leave the UK when I use this?

The room contents an assistant reads are sent to your own AI provider, under your agreement with them, not ours. That is the point worth checking before you connect one: a zero data retention agreement you hold may not cover this route. Anthropic, for one, states that data processed by third-party tools or MCP servers is not covered by ZDR.

Can I see what an assistant did?

Yes. Every action is recorded and the room owner can read that record, with the room attribution derived from the caller's own session rather than from anything the assistant claims about itself.

How do I stop it?

Revoke it in Settings, under Connected apps. It stops working on its next request. Where the underlying session cannot be closed immediately, the panel says so rather than claiming a clean kill.

Can an organisation stop this being used at all?

Yes. An organisation owner can switch AI assistant access off company-wide, which overrides every individual room switch and applies to rooms that were already switched on.