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 LlamaIndex 15 tools — connect in under 2 minutes

Name: CloudLex Legal
Availability: InStock
Author: Vinkius

docs.llamaindex.ai/en/stable/module_guides/tools/mcp

Built by Vinkius GDPR 15 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add CloudLex Legal as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

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

import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to CloudLex Legal. "
            "You have 15 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in CloudLex Legal?"
    )
    print(response)

asyncio.run(main())

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.

LlamaIndex agents combine CloudLex Legal tool responses with indexed documents for comprehensive, grounded answers. Connect 15 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

Follow these steps to integrate the CloudLex Legal MCP Server with LlamaIndex.

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.py and run: python agent.py

Explore tools

The agent discovers 15 tools from CloudLex Legal

Why Use LlamaIndex with the CloudLex Legal MCP Server

LlamaIndex provides unique advantages when paired with CloudLex Legal through the Model Context Protocol.

Data-first architecture: LlamaIndex agents combine CloudLex Legal tool responses with indexed documents for comprehensive, grounded answers

Query pipeline framework lets you chain CloudLex Legal tool calls with transformations, filters, and re-rankers in a typed pipeline

Multi-source reasoning: agents can query CloudLex Legal, a vector store, and a SQL database in a single turn and synthesize results

Observability integrations show exactly what CloudLex Legal tools were called, what data was returned, and how it influenced the final answer

CloudLex Legal + LlamaIndex Use Cases

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

Hybrid search: combine CloudLex Legal real-time data with embedded document indexes for answers that are both current and comprehensive

Data enrichment: query CloudLex Legal to augment indexed data with live information before generating user-facing responses

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying CloudLex Legal for fresh data

Analytical workflows: chain CloudLex Legal queries with LlamaIndex's data connectors to build multi-source analytical reports

CloudLex Legal MCP Tools for LlamaIndex (15)

These 15 tools become available when you connect CloudLex Legal to LlamaIndex 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 LlamaIndex

Ready-to-use prompts you can give your LlamaIndex 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 LlamaIndex

Common issues when connecting CloudLex Legal to LlamaIndex through the Vinkius, and how to resolve them.

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

CloudLex Legal + LlamaIndex FAQ

Common questions about integrating CloudLex Legal MCP Server with LlamaIndex.

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query CloudLex Legal tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.