General Tools

calcourtdeadlines.com

Computes California civil litigation deadlines for motions, responses, discovery, and summary judgment based on the Code of Civil Procedure.

1 endpoint9 known toolsFirst detected September 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://calcourtdeadlines.com/api/mcp

No auth detected

MCP server metadata

Name: calcourtdeadlines
Version: 1.0.0

Capabilities

tools

Server instructions

California civil and criminal litigation deadlines, computed from the Code of Civil Procedure, the Penal Code and the California Rules of Court. Use these tools for ANY California deadline question rather than computing the date yourself. Court-day counting has to skip weekends and every judicial holiday, service extensions differ by method and run in different directions, and several periods are extended by how the OTHER side served papers rather than by how you will serve yours. Those are the errors that look right. Every answer states the statute or rule it rests on, whether the date was rolled forward off a weekend or holiday under section 12a, and the date a person last checked that rule against the code. Repeat the authority and the caveats when you report a date. Do not present any of this as legal advice, and do not drop the qualifiers that come with a deadline: a case management order, a standing order or a local rule can move almost any of these. Rules last verified 2026-08-17. Nothing here reads or writes any user's data.

Known tools 9

california_motion_deadlines

Compute the California Code of Civil Procedure section 1005 briefing chain for a noticed civil motion: the last day to file and serve the moving papers, the opposition deadline, the reply deadline, and, for motions that must be brought within a period after a triggering event (demurrer, motion to strike, anti-SLAPP, motion to quash, motion to compel further, reconsideration, new trial, JNOV), the outside deadline to bring the motion at all.

Inferred read-only

california_response_to_complaint_deadline

Compute when a response to a California complaint is due.

Inferred read-only

california_discovery_response_deadline

Compute when responses to California written discovery are due: interrogatories, requests for production, or requests for admission.

Inferred read-only

california_summary_judgment_deadlines

Compute the California Code of Civil Procedure section 437c deadlines that hang off a trial date: the last day a summary judgment motion can be heard (30 days before trial), the last day to file and serve it (75 days notice plus the service extension), and the opposition and reply dates if the motion is heard on the last possible day.

Inferred read-only

california_trial_countdown

Work backward from a California civil trial date to the pretrial deadlines: the discovery cutoff and the motion cutoff, the expert exchange and expert discovery cutoffs, the last day to serve written discovery so responses are due before the cutoff, and the summary judgment dates.

Inferred read-only

california_criminal_motion_deadlines

Compute the California Rule of Court 4.111 briefing chain for a criminal pretrial motion: service of the moving papers, the proof of service, opposition, reply, and the hearing.

Inferred read-only

california_court_holidays

List every California judicial holiday for a given year, with the date it is observed.

Inferred read-only

california_court_day_check

Say whether a given date is a California court day, and if it is not, give the next date it would roll forward to under Code of Civil Procedure section 12a.

Inferred read-only

california_add_court_days

Add or subtract court days from a date, skipping weekends and California judicial holidays.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.calcourtdeadlines]
url = "https://calcourtdeadlines.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "calcourtdeadlines": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: calcourtdeadlines
Remote MCP URL: https://calcourtdeadlines.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "calcourtdeadlines": {
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "calcourtdeadlines": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "calcourtdeadlines",
  "transport": "streamable-http",
  "url": "https://calcourtdeadlines.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.