MCP
Connect your AI client to Colabra when it needs to investigate live deal evidence. Each user signs in with their own Colabra account; workspace and project permissions continue to apply.
Choose a plugin or a connector
| Connection | What it provides |
|---|---|
| Colabra plugin, in supported clients | Colabra workflow skills and supporting tools, plus authenticated evidence access |
| Remote MCP connector | Access to the capabilities exposed by the Colabra server in that client; it does not install local plugin skills or report helpers |
Start from Settings → Integrations in Colabra for the setup and downloads available to your workspace. Your AI workspace administrator may need to enable Colabra before individual users can connect.
The hosted MCP endpoint is:
https://api.colabra.ai/mcpUse remote HTTP MCP with OAuth. A service-account token for the REST API is a separate authentication flow.
What the connector can do
Available tools depend on the connection’s permissions and capability profile. The default review profile emphasizes current source evidence.
| Area | Available workflow |
|---|---|
| Select a deal | Identify your workspace and project before reading private evidence |
| Find evidence | Search and list files, inspect selected file details, and follow source routes |
| Read sources | Open processed source passages with version and location context |
| Compare and calculate | Query supported structured data, aggregate rows, and compare selected documents |
| Investigate entities | Find entities, linked evidence, and relationship context within the selected project |
| Follow up | Inspect requests and, when enabled and explicitly requested, create or resolve requests, add comments, or upload evidence |
The tool list exposed in your client is authoritative for that connection. Existing analysis, task, and risk-summary tools may require a broader profile. The connector does not expose the app’s complete internal findings register or the old report-create and report-generate tools.
A useful first session
Ask the client to:
- Confirm the workspace and project by name.
- Find the source evidence relevant to a specific question.
- Open the current passages before drawing material conclusions.
- Distinguish supported facts, conflicting evidence, and missing information.
- Prepare the requested answer or deliverable, with source references.
For example: “Review the customer agreements in this project for transfer restrictions. Identify the operative agreement and amendments, cite the relevant language, and draft questions for anything unresolved.”
Ask separately to save a comment, create a seller request, or upload a file when you want the project record changed. A local deliverable created by the external client is not automatically a project report.
Source coverage
MCP reads are scoped and paginated. A search hit identifies a candidate source; it is not a complete review. A passage may cover only part of a document. Clients should follow the returned source and continuation routes and retain the reported coverage limits.
The connector provides processed evidence access. It is not a bulk-download interface for the original data room. Use the app’s permitted export controls for that task.
Client guides
OAuth discovery
Clients should discover OAuth settings automatically. If manual configuration is required, use:
| Setting | URL |
|---|---|
| Authorization metadata | https://api.colabra.ai/.well-known/oauth-authorization-server |
| Protected resource metadata | https://api.colabra.ai/.well-known/oauth-protected-resource/mcp |
| Token endpoint | https://api.colabra.ai/mcp/oauth/token |
If no tools appear, check that Colabra is enabled in the current AI workspace, complete sign-in, and confirm access to the intended project. For software integrations, see the REST API overview.