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

Name: CloudLex Legal
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 15 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install CloudLex Legal and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "cloudlex-legal": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

Claude Desktop is the definitive way to connect CloudLex Legal to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 15 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

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

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using CloudLex Legal

Look for the 🔌 icon in the chat. your 15 tools are now available

Why Use Claude Desktop with the CloudLex Legal MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with CloudLex Legal through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

CloudLex Legal + Claude Desktop Use Cases

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

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

CloudLex Legal MCP Tools for Claude Desktop (15)

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

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

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

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

CloudLex Legal + Claude Desktop FAQ

Common questions about integrating CloudLex Legal MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.