Bring Litigation Management
to LangChain
Learn how to connect FinLegal to LangChain and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the FinLegal MCP Server?
Connect your FinLegal account to any AI agent and take full control of your legal claims management and case orchestration through natural conversation.
What you can do
- Claim Orchestration — List and manage legal claims programmatically, including retrieving detailed status updates and technical metadata across UK, US, and AU regions
- Claimant CRM — Manage complete profiles for contacts and claimants to maintain a high-fidelity database for your legal operations
- Workflow Automation — Programmatically create and track workflow activities (steps/forms) to ensure case progression and deadline adherence
- Template Intelligence — Access activity and attribute templates to understand valid data types and required steps for every claim type
- Case Navigation — Manage complex legal cases that act as containers for multiple individual claims to streamline high-volume legal management
How it works
1. Subscribe to this server
2. Retrieve your API Key from your FinLegal/CaseFunnel dashboard (Settings > API Keys)
3. Specify your Region (uk, us, or au) in the configuration
4. Start managing your legal operations from Claude, Cursor, or any MCP client
No more manual status checking or complex form navigation in the legal portal. Your AI acts as your dedicated legal operations and case coordinator.
Who is this for?
- Law Firms & Attorneys — instantly check claim statuses and update case activities using natural language commands
- Claim Management Companies — automate claimant onboarding and monitor large-scale legal portfolios without leaving your workspace
- Legal Ops Leads — manage contact directories and verify workflow templates through simple AI queries
Built-in capabilities (12)
Requires either claimId or contactId along with activityTemplateId. Create or back-fill an activity (step/form) for a claim or contact
Create a new legal claim for a contact
Use isAdministrator=true for claim managers. Create a new contact (Claimant or Admin)
Get details for a specific case
Get details for a specific claim
Get details for a specific contact
Find a contact by their email address
List activities associated with a claim
List available activity templates
List available attribute templates
List all claims
Update an existing contact
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with FinLegal through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine FinLegal MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across FinLegal queries for multi-turn workflows
FinLegal in LangChain
FinLegal and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FinLegal to LangChain 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 FinLegal in LangChain
The FinLegal 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 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain 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
FinLegal for LangChain
Every tool call from LangChain to the FinLegal 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 FinLegal API Key?
Log in to your account, navigate to Settings > API Keys, and generate a new key for your integration.
Which regions are supported?
The FinLegal MCP server supports uk, us, and au regions. You can specify this during setup.
Can I search for a contact by email?
Yes! Use the get_contact_by_email tool to retrieve profile details and associated claims for any registered email address.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters