# DISCO MCP for AI Agents AI Agent Connect

> DISCO lets your AI agent manage legal matters, track document ingestion, and monitor review teams through the DISCO API. It turns complex e-discovery tasks into simple conversations, allowing you to oversee metadata, tags, and user access without jumping between tabs.

## Overview
- **Category:** business-intelligence
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_pyVNRuPFueJV7nzKGL7lENH47MOOAgKyXzYzEaqw/ai-agent-connect
- **Tags:** e-discovery, datasets, data-usage, review-metrics, legal-analytics

## Description

Managing a legal matter usually means jumping between different tabs to check on document counts, see who has access to what, and verify if the right tags are being applied. With this Connector, you can just ask your AI to do the heavy lifting. You can pull up specific matter details, check the metadata for a specific file, or see which documents were uploaded recently. It takes the manual work out of monitoring your litigation workflow. You can even see which users are authorized for specific cases to keep your data secure. It's a big part of why Vinkius is the go-to for these types of integrations; it makes your agent feel like a member of your legal team who actually knows the DISCO platform. Instead of hunting for info, you just talk to your agent and get the facts you need for your next meeting or court date. You won't have to waste time manually filtering through hundreds of files just to find one custodian name or a specific tag. The integration handles the heavy lifting of querying the API so you can focus on the actual legal strategy. It turns a complex data retrieval process into a simple conversation where you get immediate answers about your matter's status and document health.

## Tools

### get_data_usage_changes_metadata
Retrieve the metadata schema for data-usage change events

### get_metrics
Pass a JSON payload to scope the query (e.g. metric name, date range, review-db filter).

Query review metrics from DISCO

### get_reviewdb_size
Pass an optional JSON payload to filter by review-db name or date.

Get the review database size metric

### list_datasets
Use the optional search to filter by name.

List datasets (matters) available in your DISCO organization

### list_reviewdb_names
List the names of available review databases

### list_data_usage_changes
g. ingest, deletion) across datasets.

List data-usage change events recorded for your datasets

## Prompt Examples

**Prompt:** 
```
List all the legal matters I have in my account.
```

**Response:** 
```
I've found the following active matters in your DISCO account:

| Matter Name | Status | Document Count |
| :--- | :--- | :--- |
| Smith vs. Jones | Active | 450 |
| Project Aurora Review | In Progress | 1,200 |

Would you like to see the specific document count for the largest matter?
```

**Prompt:** 
```
Who has access to the 'Smith vs. Jones' matter?
```

**Response:** 
```
Here are the users with explicit access to the **Smith vs. Jones** matter:

*   **Admin**: Sarah Jenkins
*   **Reviewer**: Michael Chen
*   **Reviewer**: Elena Rodriguez

Would you like to see the list of authorized users for your entire account instead?
```

**Prompt:** 
```
Show me the metadata for document 'DOC-9988'.
```

**Response:** 
```
Here is the metadata for document **DOC-9988**:

*   **Ingestion Date**: June 12th
*   **Custodian**: John Doe
*   **Tags**: Privileged, Highly Confidential

Should I pull the full audit trail for this document?
```

## Capabilities

### Pull matter details
Get specific settings and statuses for any legal matter in your account.

### Check document metadata
View the full technical properties of a specific file including custodians.

### List matter documents
See every document associated with a specific legal case.

### Monitor user access
Identify exactly who has permission to view a specific matter.

### Track recent uploads
Identify which documents were recently added to a specific matter.

### Review document tags
See the categories and taxonomies used for your legal review.

### Search matter files
Find specific keywords or metadata across documents in a matter.

### Get account info
Check your DISCO account metadata and usage limits.

### List authorized users
See every user with access to your DISCO account.

## Use Cases

### Auditing Permissions
A legal ops manager needs to ensure only the right people see a sensitive case. They ask the agent to list users for a specific matter using list_matter_access_users.

### Ingestion Monitoring
A litigation support specialist wants to know if the new batch of files arrived. They ask the agent to identify documents that were recently uploaded using list_recently_ingested_documents.

### Metadata Research
An attorney is preparing for a meeting and needs to know the custodian for a specific file. They ask the agent to pull the full technical metadata using get_document_metadata.

### Workload Overview
A paralegal wants to see all active cases. They ask the agent to list all legal matters to get a high-level summary of the current workload.

## Benefits

- Get matter statuses instantly by using list_legal_matters to see your entire workload in one list.
- Audit security by using list_matter_access_users to see exactly who can view sensitive legal cases.
- Speed up research by using search_matter_documents to find specific keywords across your entire document pool.
- Monitor ingestion progress using list_recently_ingested_documents to see what files just hit the system.
- Verify data organization by using list_document_tags to check the taxonomies your review team is using.
- Access file properties quickly with get_document_metadata to see custodians and other technical details.

## How It Works

The bottom line is you get to manage your entire e-discovery workflow through a chat interface instead of manual clicking.

1. Connect the DISCO integration to your AI client.
2. Provide your DISCO API Key and Client ID from your organization settings.
3. Ask your agent to check matter statuses, list documents, or find specific metadata.

## Frequently Asked Questions

**Can the DISCO MCP help me manage my legal matters?**
Yes, it allows you to list all legal matters in your account and retrieve detailed settings and statuses for any specific case through a chat interface.

**How do I use DISCO MCP to check document tags?**
You can ask your agent to list all tags used to categorize documents in a specific matter to see how your review team is organizing the data.

**Can my agent see who has access to my DISCO cases?**
Yes, it can pull a list of only the users who have explicit access to a specific matter, which is great for auditing permissions.

**Does DISCO MCP support searching for keywords?**
Yes, it can search for specific keywords or metadata across all documents associated with a specific legal matter.

**How does DISCO MCP help with litigation support?**
It helps litigation support teams monitor document ingestion progress and identify which files were recently uploaded to a matter.

**Can I check my account limits with DISCO MCP?**
Yes, it can retrieve your DISCO account metadata, including your current usage limits and general account info.

**How do I get DISCO API credentials?**
Log in to your DISCO account, navigate to the organization settings, and you can generate or retrieve your API Key and Client ID from the API management section.

**Can the agent download legal documents?**
This integration currently focuses on retrieving technical metadata and auditing document tags and statuses. Accessing full document content for download is managed via the DISCO platform.

**Is the integration secure for sensitive legal data?**
Yes, it uses official DISCO API protocols and only accesses the matters and documents exposed via your API key permissions, ensuring enterprise-grade security.

**Why are my requests returning 403 Access Denied?**
DISCO enforces CIDR block (IP allowlisting) verification per organization. You must add the MCP's egress IP address as a trusted source in Organization Settings → API, or every request will be rejected with 403 regardless of key correctness.