FinLegal MCP Server for CursorGive Cursor instant access to 12 tools to Create Activity, Create Claim, Create Contact, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The FinLegal app connector for Cursor is a standout in the Erp Operations category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install FinLegal and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"finlegal": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 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.
Cursor's Agent mode turns FinLegal into an in-editor superpower. Ask Cursor to generate code using live data from FinLegal and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
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
The FinLegal MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 FinLegal tools available for Cursor
When Cursor connects to FinLegal through Vinkius, your AI agent gets direct access to every tool listed below — spanning litigation-management, claim-tracking, legal-tech, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect FinLegal to Cursor via MCP
Follow these steps to wire FinLegal into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using FinLegal
Why Use Cursor with the FinLegal MCP Server
Cursor AI Code Editor provides unique advantages when paired with FinLegal through the Model Context Protocol.
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
FinLegal + Cursor Use Cases
Practical scenarios where Cursor combined with the FinLegal MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for FinLegal in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with FinLegal immediately.
"List all active legal claims."
"Create a new contact 'John Doe' with email 'john.doe@example.com'."
"Show me the workflow activities for claim 'clm_123'."
Troubleshooting FinLegal MCP Server with Cursor
Common issues when connecting FinLegal to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
FinLegal + Cursor FAQ
Common questions about integrating FinLegal MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.