Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
California Court Deadlines is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Computes California state court deadlines and cites the code section behind every date. No API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http california-court-deadlines-mcp https://calcourtdeadlines.com/api/mcp
# 2 — ask your agent for something these tools do
# california_motion_deadlines, california_response_to_complaint_deadline, california_discovery_response_deadline and 6 more
California Court Deadlines costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CAAll 1 server
calcourtdeadlines1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http california-court-deadlines-mcp https://calcourtdeadlines.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| motion | string | yes | 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-s |
| hearing_date | string | yes | 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 inte |
| service_method | string | yes | 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 |
| role | string | no | Whether you are bringing the motion (moving) or responding to it (responding). |
| trigger_date | string | no | 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 trigg |
| entry_date | string | no | 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 i |
| trigger_service_method | string | no | 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 |
| trigger_papers | string | no | 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 servic |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service_date | string | yes | 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 acknowled |
| service_method | string | yes | 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 outsid |
| case_type | string | no | Unlawful detainer runs on a different statute and a much shorter clock. |
| meet_confer_declaration | boolean | no | True if a section 430.41(a)(2) meet-and-confer declaration was filed, which takes an automatic 30 days. |
| stipulated_15_days | boolean | no | True if the parties stipulated to the rule 3.110(d) 15-day extension. |
| court_extension_days | integer | no | Days of any section 1054 court-ordered extension actually obtained. |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| served_date | string | yes | The date the discovery was served on you. |
| discovery_type | string | yes | Which set. rogs = interrogatories; rfp = requests for production; rfa = requests for admission |
| service_method | string | yes | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trial_date | string | yes | The trial date. |
| service_method | string | yes | How the moving papers will be served. Section 437c(a)(2) sets its own extension table, which is not the same as section 1013. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trial_date | string | yes | The trial date. |
| set_date | string | no | Optional. The date the trial date was set, which some local rules count from. |
| service_method | string | no | 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 extensio |
| county | string | no | Optional. Adds that county's local-rule deadlines where they are computable from the trial date. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| motion | string | yes | 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); p |
| hearing_date | string | yes | 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. |
| role | string | no | Whether you are bringing the motion or responding. |
| trigger_date | string | no | For a motion timed from an event, the date of that event (for a section 995 motion, the date of arraignment on the information). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | Four-digit year. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | The date to check. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | The date to count from. The starting day itself is not counted. |
| court_days | integer | yes | How many court days to move. Negative counts backward. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install California Court Deadlines or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish California Court Deadlines can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.