CNJ Datajud API MCP for AI. Query Brazilian Judicial Records Directly
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
CNJ Datajud API provides direct access to Brazil's national judicial records, letting you query lawsuit details and procedural history from the official government database.
You can retrieve full case metadata using a unique CNJ number, narrow results by specific legal categories or court offices, or run complex searches across date ranges and parties.
It’s essential for legal professionals needing deep visibility into the Brazilian justice system without manual portal navigation.
What your AI can do
Search processes advanced
Runs flexible, complex queries against the Datajud API by specifying various filtering parameters like dates or parties.
Search processes by class and organ
Searches for processes that match a specific legal procedural class and court organ code simultaneously.
Search process by number
Retrieves the full details of a specific lawsuit using only its unique CNJ case number.
Find all detailed information about a single lawsuit using its unique CNJ number.
Limit your search results to processes that match specific procedural classes or court organ codes.
Execute advanced queries across the entire database, filtering by dates, parties, or other metadata fields.
Ask an AI about this
Waiting for input…
CNJ Datajud API: 3 Tools
These tools allow you to perform targeted queries across the entire Brazilian judicial database using specific identifiers and advanced filtering methods.
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 CNJ (Datajud API Pública) on VinkiusSearch Processes Advanced
Runs flexible, complex queries against the Datajud API by specifying various filtering parameters like dates or parties.
Search Processes By Class And Organ
Searches for processes that match a specific legal procedural class and court organ...
Search Process By Number
Retrieves the full details of a specific lawsuit using only its unique CNJ case...
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 CNJ (Datajud API Pública), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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 CNJ Datajud. 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 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Pain of Manual Judicial Research
Today, finding a lawsuit's history means jumping between multiple government sites, logging in with different credentials, and manually cross-referencing status updates. You spend hours just tracking down the right case movement or determining if the records belong to a specific court office.
With this MCP, your agent handles the complexity. You tell it what you need—whether by number, class, or date range—and it pulls the official metadata directly. The result is clean, structured data, ready for use.
Direct Access with CNJ Datajud API
You skip logging into multiple court portals and manually cross-referencing records from various judicial bodies. You don't have to worry about which specific API alias is needed for the TRF or TST.
The MCP standardizes this process. It lets you query every required detail—from procedural class codes to complex date filters—in one single, actionable step.
What your AI can actually do with this
This MCP connects your AI client directly to the Brazilian National Council of Justice (CNJ) Datajud Public API. You can pull detailed records on lawsuits, court movements, and procedural history that used to require navigating multiple government websites. It gives you a single point of access for deep legal data across various courts—TRFs, TJs, and more.
Instead of manually filling out forms or searching through dated portals, your agent executes complex queries using official parameters. Need to know the status of a specific case? Use its unique number. Want to check all cases related to a particular type of law or court office? Filter by those codes.
If you need something really detailed, like finding processes that changed hands over the last month, you can run advanced searches.
When your AI client connects through Vinkius, it handles the connection and authentication so you just focus on the query. It’s how you get accurate legal data quickly for compliance checks, research analysis, or simply updating a client on a case status.
019e3879-ff35-7090-ace1-ab7a08b8869b Here's how it actually works
The bottom line is: You ask your AI client to look up legal records by providing context (number, type, or dates), and it gets you the official data back.
Subscribe to this MCP and enter your required CNJ Datajud API Key.
Instruct your AI client that you need data from the Brazilian judicial system. Specify whether you have a unique case number, a class/organ code, or date parameters for filtering.
Your agent executes the query against the national database and returns structured metadata about the lawsuits.
Who is this actually for?
This MCP is built for anyone who needs reliable, deep access to Brazilian judicial law. It targets professionals whose jobs depend on knowing case history, legal risk, or regulatory compliance.
Needs to quickly check the status and full history of a client's lawsuit without leaving their workflow.
Automates background checks or risk assessments against official judicial data sources for regulatory filings.
Runs bulk queries to extract legal statistics, identify trends in litigation, or support academic research.
What Changes When You Connect
Skip manual portal navigation. You can pull full case history and status updates instantly using search_process_by_number.
Automate complex filtering. Instead of running multiple searches, you use advanced queries to narrow results by dates or parties via search_processes_advanced.
Target specific legal niches. The MCP lets you search for processes matching both a procedural class and a court organ code using search_processes_by_class_and_organ.
Eliminate data silos. Access records from multiple Brazilian courts (TRFs, TJs) through one single API connection.
Speed up compliance checks. Run background legal risk assessments against the official national database in minutes.
See it in action
Checking a Client's Case Status
A lawyer needs to know the current status of a client's lawsuit filed years ago. They use search_process_by_number with the unique ID and get the last recorded court movement immediately, eliminating phone calls to the court clerk.
Analyzing Industry Risk
A compliance officer must assess all potential legal exposure for a new client sector. They run search_processes_advanced with specific industry keywords and date ranges to build a risk report.
Researching Specific Legal Procedures
A researcher wants statistics on 'Tax Execution' processes handled by the São Paulo court office. They use search_processes_by_class_and_organ to pull only those relevant records for pattern analysis.
The honest tradeoffs
Searching vaguely by keywords
Asking the agent: 'Find lawsuits about taxes.' This is too broad and gives useless results because the tool needs structured input, not natural language topics.
To search effectively, you must use a specific function. If you know the code, use search_processes_by_class_and_organ. If you have dates, use search_processes_advanced.
Ignoring unique IDs
Trying to find a case by just listing names. This fails because the system requires official judicial identifiers for accurate lookups.
If you have the full CNJ number, use search_process_by_number. It's the fastest and most accurate way to get the record.
Over-relying on a single tool
Only using one search function when the parameters are wrong. For example, trying to use search_processes_by_class_and_organ when you only know the date range.
Evaluate your input first. If dates matter most, start with search_processes_advanced. Only switch tools once you confirm which parameters you actually possess.
When It Fits, When It Doesn't
Use this MCP if your need is to access official, structured judicial records from the Brazilian system. Your search query must involve specific identifiers: a CNJ number, a procedural class/organ code, or defined date ranges. If you only know general topics (e.g., 'labor law' or 'debt'), you must first find those codes and then use this MCP to execute the lookup.
Don't use this if you need to file a complaint or take action on a case; it is purely for reading data. Don't use it if your records are housed in an internal company database; this connects only to the public CNJ API. For simple document retrieval, check general-purpose search tools instead.
Questions you might have
How do I find a case status using search_process_by_number? +
You provide the unique CNJ number to search_process_by_number. The MCP returns all associated metadata, including the current procedural class and court assignment.
Can I run a complex date search using search_processes_advanced? +
Yes. search_processes_advanced is designed for this. You input specific start/end dates along with other filters like parties to pinpoint records that changed during that window.
Do I need both class and organ codes? (Using search_processes_by_class_and_organ) +
You use search_processes_by_class_and_organ when you know two specific things: the procedural type AND the court office. It narrows the scope efficiently.
Is this MCP for private company records? +
No. This MCP connects exclusively to the public CNJ Datajud API, meaning it only handles official governmental judicial processes in Brazil.
What credentials do I need before using `search_process_by_number`? +
You must provide a valid CNJ Datajud API Key for authentication. Vinkius handles the secure storage of this key, so you just need to supply your unique credential when setting up the connection.
If I use `search_processes_advanced` and don't get results, what might be wrong? +
It usually means no processes match your specific criteria. Double-check that all date ranges and metadata filters are correctly formatted according to the Datajud API documentation.
Does `search_processes_by_class_and_organ` require unique codes for every query? +
No, you don't need a unique code set. You can run searches that cover broad ranges or multiple classes and organs in a single request.
How is the data structured when I use `search_processes_advanced`? +
The output provides detailed JSON metadata, including procedural history, parties involved, and current judicial status. It's designed to give you a complete picture of the lawsuit.
How do I find a process if I only have the CNJ number? +
Use the search_process_by_number tool. You will need the unformatted digits of the process and the specific court alias (e.g., api_publica_tjsp for São Paulo State Court).
Can I list multiple processes from a specific court organ? +
Yes, use search_processes_by_class_and_organ. Provide the court alias, the procedural class code, and the organ code. You can also control the result size and use pagination.
What is the 'Advanced Search' tool for? +
The search_processes_advanced tool allows you to send a raw Elasticsearch query body. This is useful for complex filtering that isn't covered by standard search tools, such as filtering by specific dates or nested metadata.
We've already built the connector for CNJ Datajud API. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 3 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.