MCP: Court Rules
The Court Rules MCP server gives AI agents access to structured filing rules for 20+ federal courts and 750+ judges, plus 27 state courts and 2,000+ judges. Six tools let you list courts, search judges, retrieve rules, search filing requirements, look up court holidays, and generate compliance check parameters.What you get
Six court rules tools:The same MCP server also provides three enforcement data tools for monitoring privacy enforcement
actions across 21 jurisdictions. See MCP: Enforcement Data.
Quick start
Add the server to your AI client, then sign in when the client asks. It opens console.courtrules.app in your browser, you sign in and approve the connection once, and the client keeps you signed in after that.Claude Code
/mcp in Claude Code, select court-rules, and choose Authenticate.
Claude Desktop and claude.ai
Open Settings > Connectors > Add custom connector. EnterCourt Rules as the name and https://mcp.courtrules.app/mcp as the URL, click Add, then click Connect and sign in.
Cursor
Add to~/.cursor/mcp.json, then open Cursor Settings > MCP and click the sign-in prompt next to court-rules:
VS Code
Add to.vscode/mcp.json. VS Code asks you to sign in the first time it starts the server.
Codex CLI
Scripts, backends, and clients without sign-in
Send the API key from your console dashboard asAuthorization: Bearer <api_key>. Keys do not expire. See Authentication for header configs and an SDK example.
Once connected, try asking your agent: “What are Judge Beaudet’s courtesy copy rules at LA Superior Court?”
Tool reference
list_courts
List courts with their judge counts. There are over 1,000 courts, so results come in pages: passquery to find a court, and pass next_offset back as offset to read the next page. judge_count counts judges currently sitting on the court.
Parameters:
Example request:
{ "query": "district of new york", "limit": 3 }
Example response:
next_offset is null on the last page.
search_judges
Search for judges by district, name, or type. Parameters:
Example request:
{"district_id": "ca-los-angeles-superior", "name": "beaudet"}
Example response:
get_judge_rules
Get all extracted rules for a specific judge. Parameters:
Example request:
{"judge_slug": "judge-teresa-a-beaudet", "district_id": "ca-los-angeles-superior"}
Example response:
search_filing_rules
Search extracted filing rules across active source documents. Use this for e-filing requirements, service and proof of service, filing timing, fees, courtesy copies, rejection and cure windows, and courtroom preferences. Unlikeget_judge_rules, which returns everything for one judge, this searches across courts and judges by keyword and rule type.
Parameters:
Example response:
list_court_holidays
List court holidays and closure dates. Returns the official source URL and the last time Court Rules checked that source, so you can show provenance alongside a deadline calculation. Parameters:
Example response:
check_compliance
Generate compliance check parameters for the Court Rules REST API. This tool formats your check request; the actual compliance check runs atapi.courtrules.app/api/v1/check (requires an API key).
Parameters:
This tool does not perform compliance checks directly. It generates the parameters and a curl example for calling the REST API.
Example response:
Integration patterns
Pre-filing compliance
Check documents against judge-specific rules before filing:get_judge_rules early in the drafting process so users see requirements before they finish writing, then call check_compliance as a final gate before submission.
Error handling
MCP tool calls return errors as text content, not HTTP error codes. If a tool encounters an error (invalid parameters, database unavailable), the response will contain a descriptive error message in thecontent array:
- Invalid judge_slug:
"No judge found with slug \"...\" in district \"...\"." - Invalid district_id:
"No court found with ID \"...\"." - Database error:
"Error querying courts: ..."or"Error searching judges: ..."
mcp.courtrules.app does not currently enforce rate limits on MCP tool calls.
Next steps
- REST API Quickstart to run compliance checks directly via HTTP
- Coverage Levels to understand the three rule layers (FRCP, Local Rules, Standing Orders)
- MCP: Enforcement Data for privacy enforcement tools on the same MCP server