Datasite

Set up M&A data rooms, search documents, manage access.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Datasite connector does

The Datasite MCP server connects a Datasite virtual data room — where M&A and capital raise documents sit under access control — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 19 tools that create projects and folders, upload and rename documents, search document content, and invite users or change their permissions. Sign-in is OAuth 2.0 with PKCE.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Datasite tools (19)

  • acceptDisclaimer
  • createContent
  • getAccessControl
  • getMembers
  • getProjectOverview
  • getQAStatus
  • grantFeatureAccess
  • inviteUser
  • listFolderContents
  • listProjects
  • listSubscriptions
  • manageQuestion
  • manageRole
  • searchDocuments
  • setupProject
  • updateContent
  • updateMembership
  • updatePermissions
  • uploadContent

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • OAuth scopes provide no application boundary. The resource descriptor advertises openid and profile; the authorization server adds email. All are identity claims. Consent cannot separate browsing a folder from inviting a buyer or changing a role.
  • Datasite publishes no tool list. The 19 names come from Anthropic's directory. Datasite's skills repository names seven of them; the other twelve — including every access-control tool — appear in no first-party document.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here. manageQuestion and manageRole in particular have operation sets we could not establish.
  • Document content requires a paid add-on. Datasite states semantic search is powered by Blueflame AI and must be enabled per project via a sales or support representative. Without it, searchDocuments returns an activation link rather than results, and content-level work — PII scanning, redaction checks, Q&A drafting from source — cannot run.
  • Project-level MFA blocks the connector entirely. Datasite states such projects are inaccessible through the connector and must be used at datasite.com directly.
  • Sessions expire in about 60 minutes. Long unattended passes over a large data room will hit re-authentication.
  • Renaming is irreversible through this interface, per Datasite's own skill documentation.
  • Whether an invitation is actually sent is project-dependent. Datasite's usage example says the agent creates draft invitations, with sending "available where project permits", and does not document which project settings permit it. We could not establish when a draft becomes a delivered invitation.
  • Availability is gated. Datasite's developer portal directs prospective integrators to contact developer@datasite.com, so listing in the directory does not imply open self-service access.
  • datasite.com/llms.txt contains no MCP information. It is an SEO "AI Citation Guide" listing marketing pages with citation scores, not a documentation index.

Frequently asked questions

Can the Datasite MCP server read the contents of documents in a data room?

Yes, but only through one tool and only as a paid add-on. Datasite's skills repository states that searchDocuments is the only permitted source of document content, and that it returns text passages with document names and page numbers. It requires Blueflame AI Premium Search, which Datasite says must be enabled per project by a sales or support representative.

Can the Datasite connector invite someone into a data room?

Yes. Anthropic's directory lists inviteUser, and Datasite's own documentation names inviting users to projects with specified roles and buyer or seller classifications as a connector feature. In a virtual data room, admitting the wrong party to confidential deal documents is the consequential act, so this is the tool to gate most carefully.

What OAuth scopes does the Datasite MCP server request?

Only openid and profile. Datasite's RFC 9728 resource descriptor advertised exactly those two on 2026-08-22, and its Ping authorization server advertises openid, profile and email. All are OpenID identity claims. No scope separates reading a deal document from inviting a buyer or changing permissions on a folder.

Does the Datasite MCP connector bypass my data room permissions?

No. Datasite's developer portal states the connector operates with the permissions of the authenticated user, cannot access projects the user lacks rights to, and cannot bypass or elevate existing access controls. The connector inherits your role rather than holding its own. An admin driving it therefore carries full admin reach.

Why can Claude not open one of my Datasite projects?

Almost certainly multi-factor authentication. Datasite documents that accounts with MFA enforced at the project level cannot reach those projects through the connector, and that the connector blocks the attempt and tells the user to log in at datasite.com directly. This is a deliberate gate, not a fault, and there is no connector-side workaround.

How long does a Datasite MCP session stay signed in?

About an hour. Datasite's developer portal states that its OAuth 2.0 flow with PKCE issues a time-limited Bearer token used for all subsequent API calls, and that sessions are valid for approximately 60 minutes before re-authentication is needed. Long unattended runs across a large data room will therefore hit a re-authentication prompt.

Is renaming a document through the Datasite connector reversible?

Not through the connector. Datasite's own smart-file-renaming skill states plainly that renaming is irreversible through this interface and that updateContent must not be called until the user explicitly confirms. The tool takes a metadata ID and a new name, so a bulk rename pass applies file by file with no undo path exposed.

Does using the Datasite connector send deal information outside the data room?

One published workflow does. Datasite's risk-analysis-audit skill instructs the agent to extract top customer and vendor names from data room documents and run public web searches on each. That routes counterparty names from a confidential deal to a search engine. The step is optional, and no MCP tool performs it.

Are Datasite connector actions audited?

Yes. Datasite's developer portal states that all connector activity is logged for security and compliance purposes, and that Datasite may log connector activity under its API Program Terms. Datasite also cites AES-256 encryption in transit and at rest, ISO/IEC 27001 certification, SOC 2 Type II attestation and GDPR compliance for the underlying platform.

Sources

Use it in an agent

Put Datasite to work.

Connect Datasite once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.