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.

DISCO MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: DISCO
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to DISCO through Vinkius, pass the Edge URL in the `mcps` parameter and every DISCO tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="DISCO Specialist",
    goal="Help users interact with DISCO effectively",
    backstory=(
        "You are an expert at leveraging DISCO tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in DISCO "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About DISCO MCP Server

Integrate DISCO, the leading legal technology platform, directly into your AI workflow. Manage your legal matters, monitor document ingestion and metadata, track document tags for review, and oversee your authorized users using natural language.

When paired with CrewAI, DISCO becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call DISCO tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Matter Oversight — List and retrieve detailed settings and statuses for all your legal matters in DISCO.
Document Intelligence — Access full technical metadata for documents, including custodians and file properties.
Tag Management — List and review document tags and taxonomies used for legal review and organization.
Review Team Monitoring — Track authorized users and identify teams assigned to specific legal cases.

The DISCO MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect DISCO to CrewAI via MCP

Follow these steps to integrate the DISCO MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from DISCO

Why Use CrewAI with the DISCO MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with DISCO through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

DISCO + CrewAI Use Cases

Practical scenarios where CrewAI combined with the DISCO MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries DISCO for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries DISCO, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain DISCO tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries DISCO against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

DISCO MCP Tools for CrewAI (10)

These 10 tools become available when you connect DISCO to CrewAI via MCP:

get_disco_account_metadata

Retrieve metadata and usage limits for your DISCO account

get_document_metadata

Get the full technical metadata for a specific document

get_matter_details

Get detailed settings and information for a specific legal matter

list_authorized_users

List all users with access to your DISCO account

list_document_tags

List all tags used to categorize documents in a specific matter

list_legal_matters

List all legal matters in your DISCO account

list_matter_access_users

List only the users who have explicit access to a specific matter

list_matter_documents

List all documents associated with a specific legal matter

list_recently_ingested_documents

Identify documents that have been recently uploaded to a matter

search_matter_documents

Search for specific keywords or metadata across documents in a matter

Example Prompts for DISCO in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with DISCO immediately.

"List all active legal matters."

"Show me the metadata for document 'DOC-9988'."

"Search for documents in 'Project Aurora' containing 'contract termination'."

Troubleshooting DISCO MCP Server with CrewAI

Common issues when connecting DISCO to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

DISCO + CrewAI FAQ

Common questions about integrating DISCO MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.