Supercharge your AI with UniCourt. Search millions of cases and track legal records automatically.
Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
UniCourt connects your AI agent directly to real-time legal data and court records. It lets you search millions of cases, track litigation updates automatically, and pull structured profiles for attorneys, judges, and law firms using natural language queries.
What your AI can do
Delete pacer credential
Removes current PACER account credentials from the system.
Generate token
Creates a new UniCourt access token for your account.
Get case count analytics
Retrieves analytics showing the count of cases grouped by their type.
Retrieves all available information for a single, known court case ID using get_case.
Scans millions of records to locate cases based on keywords and criteria using search_cases.
Sets up recurring checks on a case ID via track_case, notifying you when the court record updates.
Access structured data and analytics for attorneys, judges, law firms, and parties using specialized search tools (e.g., search_norm_attorney).
Requests a ZIP file containing comprehensive data exports for an entire set of cases (request_case_export).
Ask an AI about this
Compatible AI Apps
OAuth 2.0 CompatibleWaiting for input…
UniCourt MCP Server: 27 Tools for Legal Data Management
These tools let you perform every legal data operation—from searching cases to exporting bulk records—through a single, structured interface.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using UniCourt on VinkiusDelete Pacer Credential
Removes current PACER account credentials from the system.
Generate Token
Creates a new UniCourt access token for your account.
Get Case Count Analytics
Retrieves analytics showing the count of cases grouped by their type.
Get Case Export Callback
Gets the file URL once a bulk export of case data is finished processing.
Get Case
Pulls specific, detailed information for one case ID.
Get Case Update Status
Checks if an asynchronous request to update a case status has completed.
Get Document Order Callback
Gets the file URL once a court document order is ready for download.
Get Norm Attorney
Pulls detailed analytics and structured profiles for an attorney.
Get Norm Judge
Retrieves analytics and data about a specific judge's history and rulings.
Get Norm Law Firm
Gets comprehensive analytics and details on a law firm profile.
Get Norm Party
Pulls structured data and background information for any involved party (person or...
Get Pacer Credential
Reads the current status of your PACER account credentials.
Import Case
Uploads a case record directly into UniCourt's system using high priority.
Import Pacer Case
Brings a case into the system if it's missing, using PACER credentials.
Order Case Document
Initiates the process to order a specific court document by ID or name.
Request Case Export
Asks the server to compile and export all case data into a single ZIP file.
Request Case Update
Starts an asynchronous request to check for new updates on a specific case ID.
Search Cases
Searches the entire database of court cases using keywords and filters.
Search Norm Attorney
Finds normalized attorney profiles based on name or practice area.
Search Norm Judge
Locates normalized judge profiles by name or jurisdiction.
Search Norm Law Firm
Searches for law firms and returns their structured data.
Search Norm Party
Finds normalized party records using search criteria.
Search Pacer Case Locator
Performs a direct case lookup through the PACER Case Locator tool.
Track Case
Sets up automatic, scheduled updates for monitoring an ongoing legal case.
Track Norm Attorney
Schedules recurring data refreshes for a specific attorney's professional records.
Track Norm Law Firm
Sets up scheduled, recurring source updates for law firm profiles.
Update Pacer Credential
Manage PACER account credentials
Connect to your AI in seconds. Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 UniCourt, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by UniCourt. 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 connection provides 27 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually gathering case background info feels like digging through dusty archives.
Today, if you need a full picture of a party—say, their history across multiple lawsuits—you spend hours hopping between databases. You copy an ID from one screen and paste it into another tool to find associated attorneys or linked law firms. It’s tedious, prone to human error, and never gives you the complete picture.
With UniCourt MCP, your agent handles that mess. Give it a name or entity, and tools like `get_norm_party` pull together structured profiles for involved parties, related law firms (`search_norm_law_firm`), and judges. You get one clean data object instead of five separate screenshots.
UniCourt MCP Server: Getting the full history on attorneys.
Before, checking an attorney’s credentials meant calling two different services: one for basic case counts and another to pull their professional bio. You had to stitch that data together manually in a spreadsheet, losing time and context along the way.
Now, just ask your agent to get the normalized attorney profile using `get_norm_attorney`. It pulls all that structured analytics—case volume, specialization, win rates—into one go. It's immediate, accurate, and ready for use.
What your AI can actually do with this
UniCourt hooks your AI agent right into live legal data and court records. You'll use this server to search millions of filed cases, track updates on ongoing litigation, and pull detailed, structured profiles for anyone involved—attorneys, judges, firms, or parties.
To get started, you first need credentials management. Your agent can get_pacer_credential to check the current status of your PACER account details, use update_pacer_credential to manage those accounts, and even call delete_pacer_credential if you need to wipe the slate clean. If you're building a new connection, generate_token creates a fresh UniCourt access token for your agent.
When it comes to finding cases, you've got several routes. You can run a broad search across the entire court database using search_cases, letting you filter by keywords and criteria to locate records. If you know exactly what you want, get_case pulls every available detail for a specific case ID.
For direct lookups through PACER, the search_pacer_case_locator handles it. You can also bring cases into your system using high priority by calling import_case, or if a record is missing, import_pacer_case gets that case added using your existing PACER credentials. For big picture analysis, get_case_count_analytics retrieves analytics showing how many cases fall into different types.
To keep tabs on active litigation, you set up monitoring with track_case, which schedules automatic checks for a given case ID and alerts your agent when the court record changes. You can also trigger an immediate check for updates using request_case_update; whether that request finished or not, get_case_update_status tells you if it's ready.
When you need to track someone's professional life—an attorney or a law firm—you use specialized tracking tools: track_norm_attorney schedules recurring data refreshes for an attorney’s record, and track_norm_law_firm sets up scheduled updates for the entire firm profile.
For profiles on people, you've got structured search tools. You can find normalized attorneys using search_norm_attorney, or locate judges with search_norm_judge. To look up law firms, use search_norm_law_firm; for any involved party—person or entity—you check records with search_norm_party. Once you find them, your agent can pull deep details and analytics: get_norm_attorney gives comprehensive data on an attorney's history, get_norm_judge retrieves rulings and background on a judge, get_norm_law_firm provides full insights into a law firm, and get_norm_party pulls structured background info for any party.
You also have the ability to find these profiles by searching them first: you can call search_norm_attorney, search_norm_judge, or search_norm_law_firm.
When it comes to documents and exporting data, the server handles it all. You initiate a specific court document order using order_case_document, and once that document is ready for you to grab, get_document_order_callback provides the file URL. If you need to export everything, request_case_export asks the server to compile all case data into a single ZIP file; when that massive export is done processing, get_case_export_callback returns the final download link.
Finally, if you just want basic analytics on how many cases exist by type, get_case_count_analytics gives you that count.
019e3901-2e68-7229-93b4-021f75cd570a Here's how it actually works
The bottom line is that you don't write complex SQL; you just tell your AI what kind of legal information you need, and we handle the rest.
First, you subscribe to the server and pass your unique UniCourt Access Token.
Next, your AI client calls a specific tool—for example, search_cases with parameters like a keyword or date range.
Finally, the server executes the query against the legal database and passes the resulting structured data back to your agent.
Who is this actually for?
This is for anyone whose job revolves around finding connections in dense data—paralegals who track litigation schedules, researchers building market reports on IP law, or finance/insurance teams needing to assess legal risk profiles. If you're tired of copy-pasting case numbers into multiple databases just to get a full picture of someone’s history, this is for you.
Uses track_case and get_document_order_callback to monitor deadlines and ensure all necessary court filings are ordered on time.
Runs bulk queries using request_case_export or runs multiple searches (search_norm_law_firm, search_norm_party) to build large-scale data sets for academic or market analysis.
Runs deep due diligence checks by cross-referencing party histories and active cases using tools like get_norm_party to identify potential legal exposure.
What Changes When You Connect
Automate monitoring with track_case: Instead of manually checking case status daily, set up a recurring check. Your agent gets notified when the court record changes, saving you hours of repetitive work.
Deep dive into profiles: Use get_norm_party and get_norm_law_firm to build out complete background histories on involved parties—way beyond what basic search results show. This is critical for due diligence.
Consolidate data with exports: Don't pull case data piece by piece. Run request_case_export to get a single ZIP file containing all the required records, ready for immediate analysis in Excel or Python.
Seamlessly find who you need: Need an attorney? Use search_norm_attorney. The system handles the messy legal schema so your agent returns clean, usable profile data right away.
Cross-reference everything: You can combine searches—start with a case ID via get_case, then use that information to find associated parties with get_norm_party for a full picture.
See it in action
Assessing litigation risk for an acquisition.
A compliance officer needs to know if the target company has any active, high-profile legal issues. Instead of manually checking case databases, they use search_norm_party to find the corporate entity and then run get_norm_law_firm on all associated law firms. The agent pulls a complete risk report detailing current litigation exposure.
Monitoring a key court date.
A paralegal has a critical case ID (e.g., 1205934) that needs daily tracking for an upcoming hearing. They use track_case to set up automated monitoring. The agent receives an alert if any document is filed or status changes, eliminating the need for manual follow-up.
Building a market intelligence report.
A researcher needs data on patent litigation trends in a specific state. They use search_cases with filters (state, keyword) and then call request_case_export. The agent delivers a ZIP file containing thousands of records, allowing the researcher to analyze case counts by type using get_case_count_analytics.
Finding an obscure historical record.
A lawyer needs to confirm details on an attorney from five years ago. They run search_norm_attorney and then use the resulting ID with get_norm_attorney. This pulls structured professional data, confirming past cases and specialties that basic search wouldn't surface.
The honest tradeoffs
Calling every tool blindly
A user tries to pull case details by first calling get_pacer_credential, then search_cases, and finally get_case all in one prompt. This wastes tokens and forces the agent to guess which data is primary.
Always start with a search tool (search_cases or search_pacer_case_locator) to narrow the scope first. Only use get_case after you have confirmed the exact case ID from the initial search results.
Ignoring credential status
Attempting to run a complex query using an old or expired PACER account token, leading to silent API failures and bad data.
Always check your credentials first. Use get_pacer_credential or update_pacer_credential before any major operation like running import_pacer_case. This prevents dead-end calls.
Asking for a full export immediately
A user asks the agent to 'give me all data on this topic' and expects an instant file, which causes timeouts or partial exports.
Don’t expect everything at once. Use request_case_export first; it initiates the job. Then, use get_case_export_callback later to check when the ZIP file is actually ready.
When It Fits, When It Doesn't
You should use this server if your workflow requires structured data retrieval from legal records, specifically when you need to move beyond simple case lookups and build profiles of people or organizations. Use search_cases when you know keywords but not the ID. If you have a specific Case ID, go straight to get_case. Never use get_case if you don't first confirm the existence of the ID via a search tool—that’s how you minimize redundant calls and avoid API errors. Don't use this server just because your data is 'legal'; make sure you need the structure (like normalized profiles from search_norm_attorney) or the volume (bulk export with request_case_export). If all you need is a simple, non-structured keyword search, maybe there’s an alternative tool; but for deep legal data, UniCourt is the standard.
Questions you might have
How do I find a case ID before running `get_case`? +
You must first search the records using search_cases or search_pacer_case_locator. These tools return a list of IDs; use one of those results to feed into get_case.
Can I schedule automatic updates for my case using `track_case`? +
Yes. Calling track_case sets up an automated, recurring job that checks the court record on a defined schedule and alerts your agent when changes occur.
Which tool should I use to pull firm data: `get_norm_law_firm` or just searching for it? +
search_norm_law_firm finds the ID, but you need get_norm_law_firm afterwards. The latter pulls all the deep analytics and structured details that make the profile useful.
If I want a bulk export of cases, what tool do I use? Is it instant? +
Use request_case_export. This doesn't give you the file right away. You must then call get_case_export_callback later to check when the ZIP file is ready.
What process do I follow after calling `order_case_document` to actually get the file? +
You must call the get_document_order_callback tool. This function checks the status of your order and, once complete, returns a direct file URL that you can pass to your agent client.
If I need to start fresh or switch accounts, how do I manage my tokens using `generate_token`? +
Use the generate_token tool. It creates a new access token for your specific AI client session. You should run this before any data retrieval call if you are connecting a different user account.
If I suspect a case isn't in UniCourt, can I still find it using `search_pacer_case_locator`? +
Yes, the tool searches PACER directly. This bypasses the internal UniCourt index and allows you to locate cases that haven't been added or indexed into the platform yet.
Does running `search_cases` too many times quickly hit any performance limits? +
Yes, frequent searches trigger rate limiting. The API documentation specifies throttling rules for query volume. You need to build backoff logic into your agent client when executing search commands.
How can I search for court cases involving a specific company? +
Use the search_cases tool with a query like caseName:"Company Name". The agent will return a list of matching cases with their UniCourt IDs and basic details.
Can the AI automatically track a case for new updates? +
Yes! By using the track_case tool with a specific caseId, you can set up automated monitoring. You can even specify a refreshWindow like '1d' for daily updates.
Is it possible to get professional background data for an attorney? +
Absolutely. Use search_norm_attorney to find the attorney and then get_norm_attorney with their ID to retrieve detailed analytics and professional history.
We've already built the connector for UniCourt. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 27 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.