LEAP Legal MCP. Track case history and manage contacts from chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
LEAP Legal connects your AI agent directly to LEAP Software's API. You manage legal matters, contacts (cards), and case documentation using natural language.
Your agent can list active cases, pull correspondence history for a matter ID, create new client records, or update existing contact details—all without you having to switch between dashboards.
What your AI agents can do
Create new card
Creates a new contact record for either a person or an organization in your database.
Get card details
Retrieves all specific information associated with a single, existing contact card ID.
Get matter correspondence
Lists every piece of correspondence (documents, emails, appointments) attached to one case matter ID.
The agent pulls comprehensive records on specific legal matters, including status flags and key identifiers.
You create, read, and update contact information for people or organizations linked to your practice.
The agent aggregates all related materials—documents, emails, and appointments—for a given legal case ID.
You find out which specific contacts or organizations are already tied to an active matter ID.
The system lists all recognized legal matter types available for different jurisdictions (US, UK, AU, etc.).
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
LEAP Legal MCP Server: 10 Tools for Case Management
Use these tools with your AI client to create, retrieve, and modify every kind of data point—from case statuses to individual contact records.
019d75c6create new card
Creates a new contact record for either a person or an organization in your database.
019d75c6get card details
Retrieves all specific information associated with a single, existing contact card ID.
019d75c6get matter correspondence
Lists every piece of correspondence (documents, emails, appointments) attached to one case matter ID.
019d75c6get matter details
Pulls the core administrative details and metadata for a specific legal matter or case.
019d75c6get matter documents only
Lists only document files (PDFs, contracts) linked to a specific matter ID, ignoring emails or appointments.
019d75c6get matter linked cards
Retrieves a list of all contacts and organizations already attached to a specified legal matter.
019d75c6list cards
Displays an index of every contact card (people or organizations) stored in the system.
019d75c6list legal matter types
Shows all possible legal matter types for a target country code (e.g., US, UK, AU).
019d75c6list matters
Generates an index of every active and archived legal case matter ID in your firm's record.
019d75c6update existing card
Modifies details for a contact card that already exists, ensuring data accuracy.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with LEAP Legal, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
LEAP Legal connects your AI agent straight into LEAP Software's API. You manage all your legal matters, contacts, and case docs using just natural language. Your agent handles the heavy lifting—you don't have to jump between dashboards to get what you need.
When you use this server, your agent can act across three major data areas: Cases (Matters), People/Organizations (Cards), and associated files. It takes complex requests and breaks them down into simple API calls so you get one clean answer every time. You'll find it helps you manage the whole lifecycle of a legal matter without breaking stride.
Managing Legal Matters (Cases)
Need to know what cases your firm is tracking? Your agent can pull an index of every active or archived case ID using list_matters. Once you have that ID, you can get the core administrative data and metadata for that specific legal matter with get_matter_details. You'll see status flags and key identifiers right off the bat.
To understand everything attached to a case, your agent runs deep searches. It pulls all correspondence—that means every document, email, and appointment linked to a given Matter ID via get_matter_correspondence. If you only care about the paper trail, it filters that down for you, listing just PDFs or contracts using get_matter_documents_only.
You can map out who's involved in any case. The agent uses get_matter_linked_cards to pull a list of every contact or organization already attached to an active matter ID. Before you even start a new file, the system lets you see what legal matter types exist for different jurisdictions, like US, UK, or AU, using list_legal_matter_types.
This tells you exactly what schema you're working with.
Handling Client Records (Cards)
The card tools let you manage every person and organization in your database. If you need to start tracking a new client, the agent creates a brand-new contact record—a 'card'—using create_new_card. Need to fix an address or update someone’s job title? You use update_existing_card to modify details for any card that already exists.
If you just wanna check what we know about one client, the agent retrieves all specific info using get_card_details based on a single card ID.
You don't have to guess if someone is in your system. You can see an index of every contact card—people or organizations—with list_cards. These tools keep sure that when you do work on a case, the people involved are up-to-date and correctly logged against that file.
The Workflow
The agent handles the whole process for you. If you ask it to find every document related to Smith vs. Jones, it doesn't just search; it runs get_matter_correspondence, knows how to filter out the emails and appointments, and only presents the clean list of documents back to you.
If you need to confirm who is tied to a matter ID and then check their specific contact details, your agent handles those two steps sequentially. It calls get_matter_linked_cards first, identifies the card IDs, and can then use those IDs to pull deep data with get_card_details. You're keeping everything in one conversation thread.
How LEAP Legal MCP Works
- 1 You connect your LEAP API credentials to the server. This tells your AI agent how to talk to your firm's database.
- 2 Your AI client sends a natural language request, like "What documents are in Matter M-123?" The agent translates this into structured tool calls (e.g.,
get_matter_correspondence). - 3 The LEAP server executes the necessary API calls and returns raw data. Your agent processes that data—it filters, summarizes, and gives you a plain English answer.
The bottom line is: You talk to your AI client; it talks to LEAP Legal for you.
Who Is LEAP Legal MCP For?
This server targets legal professionals who spend too much time context-switching between case management tools, document repositories, and internal CRM systems. If you're tired of manually compiling a report that requires checking five different tabs just to see the full history on one client, this is for you.
You use list_matters and list_cards to quickly pull bulk data—like finding all active cases or generating a list of contacts who need an update.
When reviewing a case, you ask the agent for correspondence on a specific ID. It runs get_matter_correspondence and summarizes everything: documents, emails, appointments—instantly.
You use this to audit data integrity by running list_legal_matter_types or checking if all linked cards are up-to-date via update_existing_card.
What Changes When You Connect
- You get instant visibility into a client's full history. Instead of logging into three different tools, your agent runs
get_matter_correspondenceto pull documents, emails, and appointments for one matter ID. - Data integrity stays high because you can use the server to check and fix records. If an address changes, running
update_existing_cardmakes sure that contact card is current across all linked matters. - You always know what cases exist without guessing. Running
list_mattersgives you a clean index of every case ID, letting your agent pinpoint exactly where to start looking for data. - Relationship mapping becomes trivial. If you need to see who was involved in 'Case X,' the agent uses
get_matter_linked_cardsto pull all associated contacts instantly. - You don't have to guess what kind of case you're dealing with. The
list_legal_matter_typestool shows every recognized matter type for any jurisdiction, helping structure your data correctly.
Real-World Use Cases
The Post-Meeting Follow-Up
A paralegal attends a client meeting and notes several name changes. Instead of manually logging into the CRM to find every related contact, they ask their agent: 'Update the address for John Doe (Card ID 987) and link him to Matter M-501.' The agent runs update_existing_card and confirms the change is successful.
Audit Trail Generation
A firm administrator needs a full compliance report on an old case. They ask their agent: 'Give me all correspondence for Matter M-102.' The agent runs get_matter_correspondence, retrieving 5 documents, 3 emails, and the court date—all in one sweep.
Starting a New File
A lawyer gets a new client. They ask their agent: 'What are all the possible case types for California law?' The agent runs list_legal_matter_types to provide the list, allowing the lawyer to correctly categorize and initiate the matter before creating the first card.
Deep Dive Research
A junior associate needs to summarize a case. They ask: 'Show me only the contracts for Matter M-102.' The agent runs get_matter_documents_only, giving them clean access to just the necessary documents without being overwhelmed by emails or appointments.
The Tradeoffs
Trying to update data manually.
A user tries to remember if they updated a card, so they run list_cards and then try to figure out which one is the right ID to fix. This is slow and error-prone.
→
If you know the contact ID but suspect data is wrong, use get_card_details first to confirm the current record. Then, run update_existing_card with only the fields that need fixing.
Ignoring matter context.
A user tries to pull documents for a case by just typing the client name ('Smith'). The system throws an error because it needs the precise Matter ID, not just the name.
→
First, run list_matters to get the correct Matter ID (e.g., M-123). Then, use that specific ID when calling get_matter_correspondence or get_matter_details.
Overloading a single query.
A user tries to ask for everything—contacts, documents, and case types—in one massive prompt. The agent gets confused about the primary goal.
→
Break it down into steps. First, use list_matters to identify the scope. Second, run a specific tool like get_matter_linked_cards. Keep your prompts focused on one action at a time.
When It Fits, When It Doesn't
Use this server if you need to manage data across three interconnected layers: Cases (Matters), People/Orgs (Cards), and Files (Correspondence). You're doing legal operations, not just general document retrieval. Don't use it if your only goal is to search a file repository for keywords; that requires a dedicated document search tool. Use this when you need the AI agent to act on data—like 'Update contact X with details from document Y' or 'List every matter related to client Z.' If you can solve the problem by just reading one database index, maybe you don't need all ten tools.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by LEAP Legal. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Compiling a single case file shouldn't require opening five different tabs.
Today, compiling a full view of a client’s history is a nightmare. You start in the matter management system to get the basic details. Then you jump to the document repository for contracts. Next, you go to the CRM just to see who else was involved and then back again to check emails that might be archived somewhere else. It's clicks, tabs, copy-pasting—a massive amount of context switching.
With this MCP server, your agent does it all in one shot. You ask for the full case file on Matter M-123. The system runs `get_matter_correspondence`, pulling documents, emails, and appointments into a single, structured response. You get the answer without touching five different dashboards.
LEAP Legal MCP Server: Manage matters, contacts & documents
The manual steps that vanish are the ones where you have to guess an ID or manually link records. You don't need a paralegal to run five different reports and paste them into one Word document; your agent does the aggregation in real-time.
What's different now is the operational layer: data moves from 'stored' to 'usable.' The server ensures that every time you check a matter, you get a unified view—a true single source of truth for your entire legal practice.
Common Questions About LEAP Legal MCP
How do I list all my cases using the LEAP Legal MCP Server? +
Run list_matters. This tool pulls an index of every active and archived matter ID, giving you a full overview of your firm's current caseload.
Can I update a contact card using the LEAP Legal MCP Server? +
Yes. Use update_existing_card by providing the specific Card ID and the new data fields, ensuring you keep client records accurate across the board.
What is the difference between get_matter_documents_only and get_matter_correspondence? +
Use get_matter_correspondence when you need everything—documents, emails, and appointments. Use get_matter_documents_only if you only care about the PDF contracts or legal filings.
Do I need to know a Matter ID to list contacts? +
No, you can run list_cards to see all contacts in the system. However, if you want to link them to a specific case, use get_matter_linked_cards.
When connecting my AI agent, what credentials do I need to use any tool like get_matter_details? +
You need your LEAP API Key, Client ID, and Client Secret. These three items authorize your agent to access the matter data securely. You must provide these keys during server setup.
If I'm working in a country other than AU, UK, US, CA, or NZ, can list_legal_matter_types still work? +
No. The tool is limited to the five specified country codes (AU, UK, US, CA, NZ). For any jurisdiction outside this list, you'll need a different system.
How should I structure the JSON payload when using create_new_card? +
The tool requires a specific JSON body containing all card details. You must include necessary fields like name, organization type, and contact information for the record to save correctly.
Does calling list_matters repeatedly affect performance or hit rate limits? +
The API enforces standard rate limits to manage load. If your agent makes too many requests in a short time, it will receive a specific error code. Check the developer documentation for retry logic.
How do I find my Client ID and Secret? +
Register your application on the LEAP Developer Portal to obtain your unique Client ID and Secret.
Can I see all documents for a specific legal case? +
Yes, the get_matter_correspondence tool retrieves all documents, emails, and appointments linked to a target matter ID.
Does this server support different countries? +
Absolutely. LEAP is regionalized. Use the list_legal_matter_types tool with country codes like AU, UK, US, CA, or NZ to see relevant legal schemas.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
SurveySparrow
Collect feedback with conversational surveys that feel like chat and boost completion rates across employee and customer programs.
Deterministic Faker Data Engine
Generate thousands of mock names, addresses, and paragraphs instantly. Perfectly deterministic, 100% local, and ready for E2E testing.
Workable
Recruit top talent with an ATS that posts to 200+ job boards, screens candidates with AI, and manages the entire hiring flow.
You might also like
Sabre
Search and book flights and hotels globally using Sabre's travel technology platform — access Bargain Finder Max and PNR management.
Google Calendar
Sync and orchestrate your agenda securely — scan, schedule, and manipulate Google Calendar events natively in chat.
Bonusly
Recognize and reward your team via Bonusly — give bonuses, track points, and view leaderboards directly from any AI agent.