MCP: Court Rules
The Court Rules MCP server gives AI agents access to structured filing rules for 20+ courts and 630+ 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 Court Rules MCP server to your client. Sample data works immediately, no API key needed.Claude Code
Claude Desktop
Add to your Claude Desktop config:Cursor
Add to~/.cursor/mcp.json:
VS Code
Add to.vscode/mcp.json:
Codex CLI
Windsurf
Add to Windsurf MCP settings:Sample vs Full access
The hosted MCP server has two access tiers:
Sample data is available immediately, no sign-up needed. Try any tool to see real court rules data before authenticating.
To upgrade to full access, sign in at console.courtrules.app or contact api@courtrules.app. See Authentication for setup details.
Tool reference
list_courts
List all courts. Parameters:
Example response:
search_judges
Search for judges by district, name, or type. Parameters:
Example response:
get_judge_rules
Get all extracted rules for a specific judge. Parameters:
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:
On sample access this tool searches a narrow corpus (page limits and formatting for one EDNY
judge), so e-filing, service, fee, and courtesy copy queries return an empty
rules array with a
_notice explaining why. Authenticate for the full corpus.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