Connect these calculators to your AI assistant

Ask an assistant when your opposition is due and it will answer. It will also, quite often, be wrong: it will count calendar days where the statute says court days, miss that the day after Thanksgiving is a judicial holiday, or apply a service extension in the wrong direction. The number arrives with no citation and no way to check it. This page connects the same rules engine behind every calculator on this site directly to your assistant, so it stops guessing.

The address

Add this URL to any client that speaks the Model Context Protocol. It is free, it needs no account, and there is nothing to sign up for.

https://calcourtdeadlines.com/api/mcp

No authentication, no key, and no account. It is an open protocol endpoint rather than a feature of any one assistant, so the same address works in all of them.

Where it goes, per assistant

The URL is the same everywhere and the paste is not: some clients read a JSON file, some have a settings form, and the ones with files disagree about the key names. Here is the exact block for each.

ClientWhereWhat to put there
Claude Code.mcp.json in the project root
{
  "mcpServers": {
    "calcourtdeadlines": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
Or run: claude mcp add --transport http calcourtdeadlines https://calcourtdeadlines.com/api/mcp
Claude desktop and webSettings, then Connectors, then Add custom connectorPaste https://calcourtdeadlines.com/api/mcp as the remote MCP server URL. No authentication.
ChatGPTSettings, then ConnectorsAdd a connector, choose an MCP server, and paste https://calcourtdeadlines.com/api/mcp. On some plans this sits behind developer mode.
Continue.continue/mcpServers/calcourtdeadlines.yaml
name: calcourtdeadlines
version: 1.0.0
schema: v1
mcpServers:
  - name: calcourtdeadlines
    type: streamableHttp
    url: https://calcourtdeadlines.com/api/mcp
Cursor.cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project
{
  "mcpServers": {
    "calcourtdeadlines": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
Gemini CLI.gemini/settings.json
{
  "mcpServers": {
    "calcourtdeadlines": {
      "httpUrl": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
VS Code, GitHub Copilot.vscode/mcp.json in the workspace
{
  "servers": {
    "calcourtdeadlines": {
      "type": "http",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
Windsurf~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "calcourtdeadlines": {
      "serverUrl": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}
Zedsettings.json, under context_servers
{
  "context_servers": {
    "calcourtdeadlines": {
      "source": "custom",
      "url": "https://calcourtdeadlines.com/api/mcp"
    }
  }
}

A client that is not on this list almost certainly reads the first shape in that table. All of these files, ready to drop in, are in one small zip. The server is also listed in the Model Context Protocol registry (opens in a new tab), so some clients can find it by name.

Claude Code has a plugin as well, which adds the same server plus two skills and three commands for reporting a date and writing it to a calendar file: download the plugin. It is a convenience wrapper around this same endpoint, not a different service.

What it can answer

Nine tools, covering the calculators on this site. Your assistant picks the right one from the question you asked.

  • California civil 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.
  • California deadline to respond to a complaint. Compute when a response to a California complaint is due.
  • California discovery response deadline. Compute when responses to California written discovery are due: interrogatories, requests for production, or requests for admission.
  • 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 (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 pretrial deadlines from a trial date. 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.
  • California criminal pretrial 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.
  • California court holidays for a year. List every California judicial holiday for a given year, with the date it is observed.
  • Is this a California court day. 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.
  • Count California court days from a date. Add or subtract court days from a date, skipping weekends and California judicial holidays.

What comes back

Every deadline arrives with the section it rests on, a link to that section on leginfo, whether the date was moved off a weekend or judicial holiday (forward under CCP § 12a, forward to the next court day closer to trial under CCP § 2016.060 for a 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 timely under every reading), and the date a person last attested that rule. The tools also tell your assistant to repeat those qualifiers rather than strip them, because a date without them is the thing this site exists to replace.

Here is the answer to a demurrer noticed for September 30, 2026, where the complaint was served personally on July 24 and the moving papers go out by mail:

2026-08-24 (Monday)  Outside deadline to bring the demurrer
    30 calendar days after completion of service of the summons
    and complaint. No mail or electronic-service extension
    applies to service of a summons (CCP § 1016)
    This date was moved forward off a weekend or judicial
    holiday to the next court day, under CCP section 12a.
    Do not roll it again.
    Authority: CCP § 430.40(a)

2026-08-28 (Friday)  File and serve the moving papers
    16 court days' notice before hearing (§ 1005(b))
    + 5 calendar days for Mail within California (§ 1005(b))
    Authority: CCP § 1005(b)

Those two dates answer two different questions, and the difference is the reason this exists. The time to bring the demurrer runs from how the complaint was served on you, and a complaint served with the summons gets no extra days for mail. The notice period runs from how you serve your own papers. Answer the second question in place of the first and you get August 28 for both, which reads perfectly reasonable and is four days past the deadline to bring the demurrer.

What it does not do

  • It holds no data about you. The tools take dates and return dates. There is no account, no login and no record of what was asked.
  • It cannot reach your saved matters. That would mean handing a third-party client a token to your litigation calendar, and this site is not going to do that on the strength of an early-access feature. If you want your matters in front of an assistant today, export them from your matters as JSON and hand it over yourself. The file is written to be read by a model: every deadline carries its own authority, so no row needs another row to make sense.
  • It is not legal advice, and it is not a docketing service. The same limits that apply to the calculators apply here. A case management order, a standing order or a local rule in the department can move almost any of these dates, and no server knows what your judge did last month. See what this site does not calculate.

Why the answers are checkable

The tools do not have their own copy of the arithmetic. They call the same functions the calculators on this site call, so the server cannot quietly drift away from the page you can open and read. If a tool ever gives you a date this site does not give, that is a bug worth reporting, and it is a bug the test suite is built to make fail before it ships.

Rules on this site were attested September 29, 2026, and the last full pass over them was signed off on August 17, 2026. Every answer carries the date for the rules it used. How that verification works, and the per-rule dates, are on the methodology page. What has changed since, including every change that moved a date, is on the changelog.

If something is wrong

Send the tool name, the arguments you passed and the answer you got to errors@calcourtdeadlines.com. A deadline calculator that is wrong is worse than no calculator, and that goes double for one an assistant will repeat without checking.