6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Run a virtual data room: projects, documents, groups, diligence Q&A.
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
The Ideals MCP server connects Claude, ChatGPT or any MCP client to Ideals, a virtual data room for M&A due diligence, fundraising and litigation. Forty-six tools manage projects, documents, participant groups and diligence Q&A. Twenty write, four delete, and one invites a person into a deal room by email. Ideals' OAuth scopes separate read from write.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
add_users_to_project invites a person into a deal room by email address alone. No prior Ideals account is required in the request body. Permissions come from the groupId, not from the call.delete_documents_from_recycle_bin is irreversible. Ideals states deleted items cannot be restored. It is item-scoped rather than an empty-the-bin action, which limits but does not remove it.close_project terminates access for all participants at once, and Ideals documents closed projects as having all project endpoints inaccessible. We could not verify whether closure is reversible — no reopen operation is documented and none is exposed as a tool.rename_documents.Yes, by email address. Ideals documents the invite-participants endpoint as adding users to a project, and the request body takes only an email and a name plus the identifier of the group they land in. That group carries the document permissions, so access level is inherited rather than chosen per person. Ideals states users receive invitation emails when the group has active project access.
Files and folders, permanently. Ideals documents the action as irreversible and states that documents deleted from the recycle bin cannot be restored. The call takes a list of item identifiers, so it destroys what it is given rather than emptying the bin wholesale. A separate tool, delete_documents, only moves items to the bin, where the restore tool can still recover them.
It terminates access for every participant at once. Ideals documents closure as immediate when no date is supplied, and says a project can be closed from any status. Supplying a future date schedules it instead, and a second tool cancels a scheduled closure before it fires. Ideals also documents closed projects as having all project endpoints inaccessible.
Not yet, and the shape is narrower than it looks. Ideals marks both Q&A tools as under development and not available for active use. When live, the documentation says the backend picks the post type from the caller's Q&A role: an expert produces a draft, a coordinator produces an answer that an approver may hold. Question submitters cannot use it at all.
Yes, and this is unusual. The protected-resource metadata advertises fourteen scopes split by verb and by domain, including separate documents.read and documents.write, users.read and users.write. Ideals publishes a tool-to-scope table mapping every tool to one of them. A grant limited to the read scopes reaches no create, delete or invite tool.
No. The directory record has no permissions field at all — not a read-only label, not a read-and-write one. That absence sits over a connector that can invite participants into a deal room and permanently destroy documents. The scope separation described on this page comes from Ideals' own live OAuth metadata, not from the listing, so read it there.
A paid plan, plus integrations switched on twice. Ideals states the MCP server is available on selected paid subscription plans and that integrations must be enabled at both the corporate account level and the project level before use. Separately, the authenticating user must already be an invited participant of any project the agent touches, with project access enabled.
documentation URL in Anthropic's directory. A Scalar-rendered API reference whose underlying OpenAPI document is served at /swagger/v1/swagger.json) · retrieved 2026-08-19www-authenticate header. Authorization server https://auth.idealsvdr.com, resource https://gateway.idealsvdr.com/mcp, 14 scopes_supported. The root form returns a byte-identical 360-byte document; the path-insert form returns a zero-byte HTTP 404) · retrieved 2026-08-19https://auth.idealsvdr.com, PKCE plain and S256, grant types including authorization_code, client_credentials and refresh_token, no registration_endpoint. The /mcp path-append variant returns HTTP 404) · retrieved 2026-08-19https://gateway.idealsvdr.com/mcp returned HTTP 401 with body {"error":"Bearer token required"} and www-authenticate: Bearer resource_metadata="https://gateway.idealsvdr.com/.well-known/oauth-protected-resource/mcp". No tool was ever called and no authentication was attempted · retrieved 2026-08-19www.idealsvdr.com/robots.txt — https://www.idealsvdr.com/robots.txt (fetched 2026-08-19; User-agent: * with disallows on admin, login, search and /rooms/ paths, plus two sitemap declarations. No Content-Signal directives, and no Content-Signal response header on the API documentation host). gateway.idealsvdr.com/robots.txt and /llms.txt both return HTTP 404 · retrieved 2026-08-19llms.txt — https://www.idealsvdr.com/llms.txt (fetched 2026-08-19; vendor-published index describing Ideals as a virtual data room for M&A, due diligence and fundraising, with links to its document-management and users-and-permissions product pages) · retrieved 2026-08-19Connect Ideals once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.