Koskamo

CalCourtDeadlines MCP

An MCP server that computes California state court deadlines and cites the specific code sections behind every date. It supports civil and criminal motion deadlines, trial countdowns, discovery responses, and court holiday checks, running entirely in the browser without storing user data.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

CalCourtDeadlines MCP logo, by CalCourtDeadlines.comVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by CalCourtDeadlines.com
MCP endpoint (Streamable HTTP)
https://calcourtdeadlines.com/api/mcp
Vendor documentation

What its tools do

9 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

9 of 9 have a description · 9 of 9 declare behavior hints · 9 of 9 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to calcourtdeadlines.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Calculate civil motion filing and service deadlines
  • Determine discovery response due dates
  • Check California court holidays and court days
  • Compute trial countdown and summary judgment deadlines

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
calcourtdeadlines 1.3.0
MCP protocol negotiated in check
2025-06-18
Tools
9 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

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 moved off a weekend or holiday (forward under section 12a, forward to the next court day closer to trial under section 2016.060 for a Civil Discovery Act deadline, or back to the court day before for any other date counted backward from a hearing or trial or falling on a day a local rule names, which is this site's stated convention and is timely under every reading), and the date a person last attested that rule. 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 verified on 2026-09-29; each answer carries the date for the rules it used. Nothing here reads or writes any user's data.

Tools

9 advertised

california_motion_deadlines — California civil motion deadlines
Advertised by the server during the last successful anonymous check.
Advertised read-only

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. New trial and JNOV are the exception to the section 1005 chain: they are briefed under section 659a, counted forward (brief 10 days after the notice of intention is filed, opposition 10 days after the brief is served, reply 5 days after that), with the section 660(c) last day for the court to rule. Returns each date with the statute it rests on and whether it was moved off a weekend or judicial holiday: forward under section 12a for a period that runs forward, or back to the preceding court day for a count backward from the hearing, which is this site's stated convention. Use this instead of computing California motion deadlines yourself.

california_motion_deadlines input schema
{
  "type": "object",
  "required": [
    "motion",
    "hearing_date",
    "service_method"
  ],
  "properties": {
    "role": {
      "enum": [
        "moving",
        "responding"
      ],
      "type": "string",
      "description": "Whether you are bringing the motion (moving) or responding to it (responding)."
    },
    "motion": {
      "enum": [
        "compel-further",
        "compel-initial",
        "protective-order",
        "demurrer",
        "motion-to-strike",
        "judgment-on-pleadings",
        "quash-service",
        "anti-slapp",
        "msj",
        "reconsideration",
        "new-trial",
        "jnov",
        "preference",
        "reopen-discovery",
        "compel-arbitration",
        "ex-parte"
      ],
      "type": "string",
      "description": "Which motion. compel-further = Motion to compel further responses; compel-initial = Motion to compel initial responses; protective-order = Motion for protective order; demurrer = Demurrer; motion-to-strike = Motion to strike; judgment-on-pleadings = Motion for judgment on the pleadings; quash-service = Motion to quash service of summons; anti-slapp = Anti-SLAPP special motion to strike; msj = Motion for summary judgment / adjudication; reconsideration = Motion for reconsideration; new-trial = Motion for new trial; jnov = Motion for judgment notwithstanding the verdict; preference = Motion for trial preference; reopen-discovery = Motion to reopen discovery; compel-arbitration = Motion to compel arbitration; ex-parte = Ex parte application"
    },
    "entry_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "new-trial and jnov only: the date judgment was entered. Section 659(a)(2) ends the time 180 days after entry if that comes before 15 days after notice of entry, and with no notice of entry served it is the only limit. Give it whenever it is known."
    },
    "hearing_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The hearing date, as reserved with the department. EXCEPT for new-trial and jnov, which are briefed under section 659a and do not count back from a hearing: for those, give the date the notice of intention was filed (moving party) or the date the moving brief was served on you (responding party)."
    },
    "trigger_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "For a motion that must be brought within a period after an event, the date of that event (for a demurrer to a complaint served with the summons, the date service of the summons was complete, see trigger_papers; for new-trial and jnov, the first service of notice of entry of judgment, by the clerk or by any party). Omit for motions timed only off the hearing date."
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight",
        "mail-sos"
      ],
      "type": "string",
      "description": "How the MOVING PAPERS will be served. This drives the section 1005(b) notice period. For new-trial and jnov it is how the moving brief is served, which extends the section 659a opposition period under section 1013, and under section 1010.6 for electronic service made before January 1, 2027. From that date electronic service adds no time (AB 540, Stats. 2026, ch. 263). Not the same question as trigger_service_method."
    },
    "trigger_papers": {
      "enum": [
        "summons",
        "served",
        "answer"
      ],
      "type": "string",
      "description": "For demurrer, motion-to-strike and anti-slapp only: which papers started the clock. summons = the complaint or cross-complaint served with a summons (the default); trigger_date is then the date service was COMPLETE (delivery for personal service, the 10th day after mailing for substituted service or mail outside California, the signing date for notice and acknowledgment), and no service extension applies. served = an amended complaint, or a cross-complaint served on a party that has appeared; 30 days (60 for anti-slapp) after service, extended under sections 1013 and 1010.6 by trigger_service_method. answer = an answer or amended answer (demurrer and motion-to-strike only); 10 days after service, extended the same way. Ignored for other motions."
    },
    "trigger_service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight",
        "mail-sos"
      ],
      "type": "string",
      "description": "How the TRIGGERING papers were served ON the moving party. This is a different question from service_method and only this one extends the time to BRING the motion under section 1013. It never extends a period that runs from service of a summons: section 1016 takes service of a summons outside sections 1010.6 and 1013, so for a complaint served with the summons it is ignored. The common case is a complaint served personally and a demurrer served electronically. Defaults to personal, which adds nothing, so an unknown answer errs early rather than granting days that were not earned."
    }
  },
  "additionalProperties": false
}
california_motion_deadlines annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_response_to_complaint_deadline — California deadline to respond to a complaint
Advertised by the server during the last successful anonymous check.
Advertised read-only

Compute when a response to a California complaint is due. Handles the four service methods separately, because each completes service on a different day, and applies the extensions a defendant may claim: the section 430.41 meet-and-confer declaration, the rule 3.110(d) stipulated 15 days, and a court-ordered extension. Unlawful detainer runs on section 1167 instead and is handled as its own case type.

california_response_to_complaint_deadline input schema
{
  "type": "object",
  "required": [
    "service_date",
    "service_method"
  ],
  "properties": {
    "case_type": {
      "enum": [
        "general-civil",
        "unlawful-detainer"
      ],
      "type": "string",
      "description": "Unlawful detainer runs on a different statute and a much shorter clock."
    },
    "service_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date on the proof of service. What it means depends on the method: for personal service the date of delivery, for substituted service the date of the substituted delivery, for notice and acknowledgment the date the defendant signed."
    },
    "service_method": {
      "enum": [
        "personal",
        "substituted",
        "mail-outside-state",
        "notice-and-acknowledgment"
      ],
      "type": "string",
      "description": "How the summons and complaint were served. personal = Personal delivery; substituted = Substituted service (left with someone, then mailed); mail-outside-state = First-class mail to a defendant outside California; notice-and-acknowledgment = Notice and acknowledgment of receipt"
    },
    "stipulated_15_days": {
      "type": "boolean",
      "description": "True if the parties stipulated to the rule 3.110(d) 15-day extension."
    },
    "court_extension_days": {
      "type": "integer",
      "maximum": 30,
      "minimum": 0,
      "description": "Days of any section 1054 court-ordered extension actually obtained."
    },
    "meet_confer_declaration": {
      "type": "boolean",
      "description": "True if a section 430.41(a)(2) meet-and-confer declaration was filed, which takes an automatic 30 days."
    }
  },
  "additionalProperties": false
}
california_response_to_complaint_deadline annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_discovery_response_deadline — California discovery response deadline
Advertised by the server during the last successful anonymous check.
Advertised read-only

Compute when responses to California written discovery are due: interrogatories, requests for production, or requests for admission. Takes the date the discovery was served and how it was served, applies the section 1013 extension for that method (or the section 1010.6 extension for electronic service made before January 1, 2027, which AB 540 removes for service on or after that date), and rolls the result off weekends and judicial holidays under section 12a.

california_discovery_response_deadline input schema
{
  "type": "object",
  "required": [
    "served_date",
    "discovery_type",
    "service_method"
  ],
  "properties": {
    "served_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date the discovery was served on you."
    },
    "discovery_type": {
      "enum": [
        "rogs",
        "rfp",
        "rfa"
      ],
      "type": "string",
      "description": "Which set. rogs = interrogatories; rfp = requests for production; rfa = requests for admission"
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight",
        "mail-sos"
      ],
      "type": "string",
      "description": "How the discovery was served on you. This is what the section 1013 and 1010.6 extensions key to. Electronic service made on or after January 1, 2027 adds nothing."
    }
  },
  "additionalProperties": false
}
california_discovery_response_deadline annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_summary_judgment_deadlines — California summary judgment deadlines
Advertised by the server during the last successful anonymous check.
Advertised read-only

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 (81 days' notice plus the service extension; electronic service made on or after January 1, 2027 adds none), and the opposition and reply dates if the motion is heard on the last possible day.

california_summary_judgment_deadlines input schema
{
  "type": "object",
  "required": [
    "trial_date",
    "service_method"
  ],
  "properties": {
    "trial_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The trial date."
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight"
      ],
      "type": "string",
      "description": "How the moving papers will be served. Section 437c(a)(2) sets its own extension table, which is not the same as section 1013."
    }
  },
  "additionalProperties": false
}
california_summary_judgment_deadlines annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_trial_countdown — California pretrial deadlines from a trial date
Advertised by the server during the last successful anonymous check.
Advertised read-only

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. Optionally adds the local-rule deadlines for one of the counties this site tracks.

california_trial_countdown input schema
{
  "type": "object",
  "required": [
    "trial_date"
  ],
  "properties": {
    "county": {
      "enum": [
        "los-angeles",
        "san-diego",
        "orange",
        "riverside",
        "san-bernardino",
        "santa-clara",
        "alameda",
        "sacramento",
        "fresno"
      ],
      "type": "string",
      "description": "Optional. Adds that county's local-rule deadlines where they are computable from the trial date."
    },
    "set_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Optional. The date the trial date was set, which some local rules count from."
    },
    "trial_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The trial date."
    },
    "service_method": {
      "enum": [
        "electronic",
        "personal",
        "mail-ca",
        "mail-os",
        "mail-intl",
        "overnight"
      ],
      "type": "string",
      "description": "How the summary judgment papers and the section 998 offer would be served. It sets the section 437c rows and the last day to serve a section 998 offer, which takes the section 1013 and 1010.6 extensions. No published decision applies section 1013(c) or 1010.6 to a 998 offer; the tool applies both on the reasoning of Lecuyer v. Sunset Trails Apts. (2004) 120 Cal.App.4th 920, which decided a mailed offer."
    }
  },
  "additionalProperties": false
}
california_trial_countdown annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_criminal_motion_deadlines — California criminal pretrial motion deadlines
Advertised by the server during the last successful anonymous check.
Advertised read-only

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. Also gives the outside deadline for motions that run from a triggering event, such as the Penal Code section 995 motion and the section 1510 tracks. There is no service-method extension in criminal motions; rule 4.111 does not provide one.

california_criminal_motion_deadlines input schema
{
  "type": "object",
  "required": [
    "motion",
    "hearing_date"
  ],
  "properties": {
    "role": {
      "enum": [
        "moving",
        "responding"
      ],
      "type": "string",
      "description": "Whether you are bringing the motion or responding."
    },
    "motion": {
      "enum": [
        "pc-995",
        "pc-1510-outside-deadline",
        "pc-1510-outside-deadline-misdemeanor",
        "pc-1424",
        "pc-1538-5-prelim",
        "pc-1538-5-special-hearing",
        "pitchess-criminal",
        "pc-1054-5-compel",
        "pc-1054-7-disclosure",
        "pc-1050-continuance",
        "pc-1049-prepare",
        "crc-4-110-information"
      ],
      "type": "string",
      "description": "Which motion. pc-995 = Motion to set aside the information or indictment (§ 995); pc-1510-outside-deadline = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, felony (§ 1510); pc-1510-outside-deadline-misdemeanor = Deadline to preserve pretrial writ review of a § 995 or § 1538.5 denial, misdemeanor (§ 1510); pc-1424 = Motion to recuse the district attorney (§ 1424); pc-1538-5-prelim = Motion to suppress at the preliminary hearing (§ 1538.5(f)); pc-1538-5-special-hearing = Special suppression hearing in superior court (§ 1538.5(i)); pitchess-criminal = Pitchess motion, criminal (Evid. Code § 1043(a)(2)); pc-1054-5-compel = Motion to compel criminal discovery (§ 1054.5(b)); pc-1054-7-disclosure = Reciprocal discovery disclosure deadline (§ 1054.7); pc-1050-continuance = Motion to continue (§ 1050(b)); pc-1049-prepare = Time to prepare for trial (§ 1049); crc-4-110-information = Information after a holding order (CRC 4.110)"
    },
    "hearing_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The hearing date. For the section 1538.5(i) special hearing, this is instead the date notice was given to the People, because that clock runs forward."
    },
    "trigger_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "For a motion timed from an event, the date of that event (for a section 995 motion, the date of arraignment on the information)."
    }
  },
  "additionalProperties": false
}
california_criminal_motion_deadlines annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_court_holidays — California court holidays for a year
Advertised by the server during the last successful anonymous check.
Advertised read-only

List every California judicial holiday for a given year, with the date it is observed. These are the days excluded when counting court days and the days a deadline rolls off under Code of Civil Procedure section 12a. Includes the weekend-observed shifts, which are the ones most often got wrong.

california_court_holidays input schema
{
  "type": "object",
  "required": [
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 2000,
      "description": "Four-digit year."
    }
  },
  "additionalProperties": false
}
california_court_holidays annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_court_day_check — Is this a California court day
Advertised by the server during the last successful anonymous check.
Advertised read-only

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. Use this before asserting that a filing date or a deadline falls on a working day.

california_court_day_check input schema
{
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date to check."
    }
  },
  "additionalProperties": false
}
california_court_day_check annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
california_add_court_days — Count California court days from a date
Advertised by the server during the last successful anonymous check.
Advertised read-only

Add or subtract court days from a date, skipping weekends and California judicial holidays. Use this for any period a statute states in court days rather than calendar days, such as the nine and five court day opposition and reply periods under Code of Civil Procedure section 1005(b). Counting court days by hand is where most deadline errors come from.

california_add_court_days input schema
{
  "type": "object",
  "required": [
    "date",
    "court_days"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "The date to count from. The starting day itself is not counted."
    },
    "court_days": {
      "type": "integer",
      "maximum": 365,
      "minimum": -365,
      "description": "How many court days to move. Negative counts backward."
    }
  },
  "additionalProperties": false
}
california_add_court_days annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (3 of 3 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
434 ms
95th percentile latency
434 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 434 ms · metadata changed · 9 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http calcourtdeadlines-mcp https://calcourtdeadlines.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add calcourtdeadlines-mcp --url https://calcourtdeadlines.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable calcourtdeadlines-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "calcourtdeadlines-mcp": {
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "calcourtdeadlines-mcp": {
      "type": "streamableHttp",
      "url": "https://calcourtdeadlines.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start calcourtdeadlines-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "calcourtdeadlines-mcp": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http calcourtdeadlines-mcp https://calcourtdeadlines.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://calcourtdeadlines.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "calcourtdeadlines-mcp": {
      "serverUrl": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like CalCourtDeadlines MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run CalCourtDeadlines MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing