Bring Legal Practice Management
to LlamaIndex
Learn how to connect Lexzur to LlamaIndex and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Lexzur MCP Server?
Connect your Lexzur (formerly App4Legal) account to any AI agent and take full control of your legal practice management and automated case workflows through natural conversation.
What you can do
- Matter & Litigation Orchestration — List and manage your entire portfolio of high-fidelity Corporate Matters and Litigation Cases programmatically, retrieving detailed status and metadata
- Contact Intelligence — Access your complete directory of high-fidelity contacts and companies to coordinate your organizational relationship ecosystem in real-time
- Case Lifecycle Monitoring — Access real-time updates for legal cases and retrieve high-fidelity history for specific matters directly through your agent
- Legal Discovery Management — Query specific matters or contacts using custom search filters to maintain a perfectly coordinated audit trail of your legal practice
- Operational Monitoring — Verify account-level API connectivity and monitor practice volume directly through your agent for instant performance reporting
How it works
1. Subscribe to this server
2. Retrieve your API Token and Instance URL from your Lexzur dashboard (Settings > API)
3. Start orchestrating your legal practice from Claude, Cursor, or any MCP client
No more manual logging into complex legal dashboards or missing case updates. Your AI acts as your dedicated legal coordinator and matter architect.
Who is this for?
- Lawyers & Attorneys — instantly retrieve case summaries and matter statuses using natural language commands
- Legal Operations — monitor practice health and verify contact metadata without leaving your workspace
- Paralegals — automate the management of corporate records and contact directories through simple AI queries
Built-in capabilities (10)
Create a new legal matter
Get details for a specific matter
List companies/clients
List contacts
List uploaded documents
List legal invoices
List litigation cases
List legal matters
List legal tasks
List time entries
Why LlamaIndex?
LlamaIndex agents combine Lexzur tool responses with indexed documents for comprehensive, grounded answers. Connect 10 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.
- —
Data-first architecture: LlamaIndex agents combine Lexzur tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Lexzur tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Lexzur, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Lexzur tools were called, what data was returned, and how it influenced the final answer
Lexzur in LlamaIndex
Lexzur and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lexzur to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Lexzur in LlamaIndex
The Lexzur 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Lexzur for LlamaIndex
Every tool call from LlamaIndex to the Lexzur MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Lexzur API Token?
Log in to your account, navigate to Settings > API, and copy your unique access token from the credentials section.
Can I retrieve litigation cases via AI?
Yes! The list_litigation_cases tool allows your agent to retrieve high-fidelity data for all ongoing court cases in your Lexzur portfolio.
How do I search for a specific contact?
Use the list_lexzur_contacts tool and provide search parameters to retrieve high-fidelity metadata for specific individuals or companies.
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 Lexzur tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp