Bring Legal Practice Management
to Cursor
Learn how to connect Lexzur to Cursor 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 Cursor?
Cursor's Agent mode turns Lexzur into an in-editor superpower. Ask Cursor to generate code using live data from Lexzur and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Lexzur in Cursor
Lexzur and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lexzur to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.