What features of CloudLex are available through this API?

The API provides access to: Cases/Matters (CRUD operations), Contacts/Clients (create and list), Documents (list by case), Tasks (list by case), Medical Records (list by case), Liens (list by case), Communications (list by case), and Expenses (list by case). You can search cases by keyword, filter by status and practice area, and view all cases for a specific client.

How do I get a CloudLex API key?

Log in to your CloudLex account at cloudlex.com, navigate to Settings → Integrations or API Settings, and generate an API key. The key gives you access to your firm's case data, client information, documents, medical records, and expenses. Contact CloudLex support if you don't see the API option in your account.

Can I create new cases and clients through the API?

Yes! You can create new cases with case name, client assignment, status, practice area, and incident date. You can also create new contacts with first name, last name, email, phone, and contact type (Client, Opposing Party, Witness, Medical Provider, Expert). Use `create_cloudlex_case` and `create_cloudlex_client` tools for these operations.

What types of contacts can I manage in CloudLex?

CloudLex supports multiple contact types essential for personal injury practice: Clients (injured parties), Opposing Parties (defendants, insurance adjusters), Witnesses (eyewitnesses, expert witnesses), Medical Providers (doctors, hospitals, physical therapists), and Experts (medical experts, accident reconstructionists, economists). Each contact type can be linked to specific cases and communications.

CloudLex Legal MCP Server for CrewAI 15 tools — connect in under 2 minutes

Name: CloudLex Legal
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 15 Tools Framework

Connect your CrewAI agents to CloudLex Legal through Vinkius, pass the Edge URL in the `mcps` parameter and every CloudLex Legal 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="CloudLex Legal Specialist",
    goal="Help users interact with CloudLex Legal effectively",
    backstory=(
        "You are an expert at leveraging CloudLex Legal 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 CloudLex Legal "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 15 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 CloudLex Legal MCP Server

Connect to CloudLex Legal case management platform and manage your entire personal injury practice from any AI agent. Access cases, clients, documents, medical records, liens, tasks, communications, and expenses—all through a unified API designed for plaintiff personal injury law firms.

When paired with CrewAI, CloudLex Legal becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CloudLex Legal 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

Cases/Matters — List, search, create, and update personal injury cases with status, client, and practice area
Clients/Contacts — Manage your client database including individuals, opposing parties, witnesses, medical providers, and experts
Client Portfolio — View all cases associated with a specific client
Documents — Access case documents including pleadings, correspondence, evidence, and settlement documents
Tasks — View and manage tasks associated with cases including due dates and assigned attorneys
Medical Records — Access medical treatment records, bills, provider information, and medical summaries
Liens — Track medical liens, insurance liens, and other claims against settlements
Communications — View emails, phone calls, letters, and notes with clients, opposing counsel, and other parties
Expenses — Track case-related expenses including court costs, expert witness fees, and medical record retrieval costs

The CloudLex Legal MCP Server exposes 15 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 CloudLex Legal to CrewAI via MCP

Follow these steps to integrate the CloudLex Legal 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 15 tools from CloudLex Legal

Why Use CrewAI with the CloudLex Legal MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with CloudLex Legal 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

CloudLex Legal + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries CloudLex Legal 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 CloudLex Legal, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain CloudLex Legal 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 CloudLex Legal against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

CloudLex Legal MCP Tools for CrewAI (15)

These 15 tools become available when you connect CloudLex Legal to CrewAI via MCP:

create_cloudlex_case

USE WHEN: - User wants to open a new legal case - User needs to create a new matter for a client - User asks to "create a new case" or "open a matter" PARAMETERS: - case_name (REQUIRED): Case/matter name - client_id (OPTIONAL): ID of the client this case belongs to - status (OPTIONAL): Initial status — "Open" (default), "Closed", "Pending", "Settled" - practice_area (OPTIONAL): Practice area (e.g. "Personal Injury", "Mass Tort", "Auto Accident") - description (OPTIONAL): Case description/notes - incident_date (OPTIONAL): Date of the incident (YYYY-MM-DD) EXAMPLES: - "Create a new case called 'Smith Auto Accident'" → call with case_name="Smith Auto Accident" - "Open a new personal injury matter for client 456" → call with case_name="State v. Johnson", client_id="456", practice_area="Personal Injury" Create a new case/matter in CloudLex Legal

create_cloudlex_client

USE WHEN: - User wants to add a new client - User needs to create a new contact record - User asks to "add a new client" or "create a contact" PARAMETERS: - first_name (REQUIRED): Client's first name - last_name (REQUIRED): Client's last name - email (OPTIONAL): Client's email address - phone (OPTIONAL): Client's phone number - type (OPTIONAL): Contact type — "Client" (default), "Opposing Party", "Witness", "Medical Provider", "Expert" EXAMPLES: - "Add a new client John Smith" → call with first_name="John", last_name="Smith" - "Create contact for opposing party Jane Doe, jane@example.com" → call with first_name="Jane", last_name="Doe", email="jane@example.com", type="Opposing Party" Create a new client/contact in CloudLex Legal

get_client_cloudlex_cases

Useful for understanding a client's full legal portfolio and case history. Get all cases/matters for a specific client/contact

get_cloudlex_case

Get detailed information for a specific case/matter

get_cloudlex_client

Get detailed information for a specific client/contact

list_cloudlex_cases

Supports filtering by status, practice area, client, and date range for flexible queries. USE WHEN: - User wants to see all their legal cases/matters - User needs to find cases by status, client, or practice area - User is exploring their law firm's caseload - User asks "what cases do I have" or "list my open cases" PARAMETERS: - status (OPTIONAL): Filter by case status (e.g. "Open", "Closed", "Pending", "Settled") - practice_area (OPTIONAL): Filter by practice area (e.g. "Personal Injury", "Mass Tort", "Auto Accident") - client_id (OPTIONAL): Filter by specific client ID - page (OPTIONAL): Page number for pagination - page_size (OPTIONAL): Results per page (default: 25, max: 100) EXAMPLES: - "List all my open cases" → call with status="Open" - "Show my personal injury matters" → call with practice_area="Personal Injury" - "List all cases" → call with no params List all cases/matters in CloudLex Legal

list_cloudlex_clients

USE WHEN: - User wants to see all their clients and contacts - User needs to find a client by name or email - User is exploring their contact database - User asks "list my clients" or "show all contacts" PARAMETERS: - page (OPTIONAL): Page number for pagination - page_size (OPTIONAL): Results per page (default: 25, max: 100) EXAMPLES: - "List all my clients" → call with no params - "Show my contacts" → call with no params - "List clients page 2" → call with page="2" List all clients/contacts in CloudLex Legal

list_cloudlex_communications

List communications for a specific case

list_cloudlex_documents

List documents for a specific case/matter

list_cloudlex_expenses

List expenses for a specific case

list_cloudlex_liens

List liens for a specific case

list_cloudlex_medical_records

List medical records for a specific case

list_cloudlex_tasks

List tasks for a specific case/matter

search_cloudlex_cases

Search cases/matters by keyword query

update_cloudlex_case

Update an existing case/matter in CloudLex Legal

Example Prompts for CloudLex Legal in CrewAI

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

"List all my open personal injury cases in CloudLex."

"Show me all medical records for the Smith Auto Accident case."

"Create a new case for client John Smith called 'Smith v. ABC Corporation - Workplace Injury'."

Troubleshooting CloudLex Legal MCP Server with CrewAI

Common issues when connecting CloudLex Legal 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.

CloudLex Legal + CrewAI FAQ

Common questions about integrating CloudLex Legal 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.