Datasite
by Datasite
Set up M&A data rooms, search document content, and manage who has access from an AI agent. 19 tools, OAuth 2.0 with PKCE, and identity-only scopes that do not separate reading a deal document from inviting a buyer into it.
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.
Connect Datasite via MCP
https://mcp.global.datasite.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Datasite Tools & Capabilities (19)
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
openidandprofile; the authorization server addsemail. 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.
manageQuestionandmanageRolein 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,
searchDocumentsreturns 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.comdirectly. - 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.txtcontains no MCP information. It is an SEO "AI Citation Guide" listing marketing pages with citation scores, not a documentation index.
Frequently asked questions
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.
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.
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.
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.
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.
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.
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.
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.
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
- Datasite developer portal, "MCP Server" guide (retrieved 2026-08-22). The page is client-rendered and returns one word of text to a plain fetch; the 1,566-word guide was read from the React Server Component payload embedded in the same response. · retrieved 2026-08-22
- Datasite agent skills repository,
DatasiteAI/mcp-skillsat commit27ac023(retrieved 2026-08-22). Eight skills authored by Blueflame AI; the only first-party source naming tools. · retrieved 2026-08-22 - Datasite RFC 9728 protected-resource metadata (retrieved 2026-08-22). A nonsense sibling path returned a distinct 404 body, confirming the descriptor is genuine and not a catch-all. · retrieved 2026-08-22
- Datasite authorization server metadata — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Live authentication check: an anonymous
initializetohttps://mcp.global.datasite.com/mcpreturned HTTP 401 withwww-authenticate: Key(2026-08-22) · retrieved 2026-08-22 - Datasite
llms.txt(retrieved 2026-08-22). An SEO citation guide; no MCP content. · retrieved 2026-08-22 - Datasite API Program Terms — · Privacy Notice
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Datasite support (Datasite Assist) — · <mailto:service@datasite.com>
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Datasite
- Tools
- 19
- Domain
- mcp.global.datasite.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.