Chat now (no install)
Click below to open Claude or ChatGPT with the full Judit documentation preloaded as context. Best for one-off questions or quick exploration.Chat with Claude
Opens Claude.ai with the full docs preloaded. Zero install.
Chat with ChatGPT
Opens ChatGPT with the full docs preloaded. Zero install.
Install the MCP server
For repeated use across Claude Desktop, Cursor, Claude Code, ChatGPT, or any other MCP-compatible client, install the MCP server once and the tools become available natively in your chat:MCP server URL
https://docs.judit.io/mcp- Claude Desktop
- Cursor
- Claude Code
- ChatGPT
- Other clients
Open Claude Desktop, go to Settings → Developer → Edit Config, and add:Restart Claude Desktop. The judit tools appear in the chat input.
What it does
Once connected (via either path above), the AI gets two tools it uses automatically when you ask anything Judit-related:| Tool | Purpose |
|---|---|
search_judit_docs | Full-text search across every page of this documentation, returning the most relevant excerpts with their paths. |
query_docs_filesystem_judit_docs | Read any specific doc page by path (cat, head, rg, etc.) when the AI needs the full context. |
Example prompts
- “How do I create a tracking by CNJ? Show me the exact request body.”
- “What’s the difference between Hot Storage and a regular request?”
- “Write a Python snippet that creates a request, polls until it’s done, and prints the lawsuits.”
- “Which filters can I pass to
subject_codes? Cite the page.” - “Walk me through the criminal execution flow end to end.”
What it does not do
This MCP reads documentation only. It does not call the Judit API on your behalf — no real lawsuits are queried, no requests are created, no costs are incurred. To actually hit the API, use one of these:Postman Collection
Run live requests with prefilled bodies and auto-captured
request_id chaining.REST API
Call the endpoints directly from your code with your
api-key.The MCP server is hosted by our documentation platform and stays in sync with this site automatically. Every doc update is reflected in the MCP responses on the next call — no version pinning, no redeploy needed on your side.