FederalCourtDeadlines MCP server: configuration for every client.

Endpoint: https://federalcourtdeadlines.com/api/mcp
Transport: streamable HTTP. No authentication, no key, no account.

This is an open Model Context Protocol endpoint, not a feature of any one
assistant. The URL is identical everywhere; only the file it goes in and
the key names around it change. Copy the file for your client to the path
below, or paste its contents into the config you already have.

  claude-code/.mcp.json                  project root
  cursor/mcp.json                        .cursor/mcp.json, or ~/.cursor/mcp.json
  vscode/mcp.json                        .vscode/mcp.json in the workspace
  windsurf/mcp_config.json               ~/.codeium/windsurf/mcp_config.json
  zed/settings.json                      merge into Zed settings.json
  gemini-cli/settings.json               .gemini/settings.json
  continue/federalcourtdeadlines.yaml    .continue/mcpServers/
  generic/mcp.json                       any other client that reads mcpServers

Claude desktop and web, and ChatGPT, have no config file. Add a custom
remote MCP connector in settings and paste the endpoint.

Three tools: federal_deadline (one FRCP, FRAP 4 or removal deadline),
federal_legal_holidays (the Rule 6(a)(6) legal holidays for a year, 2024
to 2030), and federal_count_days (a period counted under FRCP 6(a) or
FRAP 26(a)). Every answer carries the rule behind it, the earliest and
latest dates where the readings differ, and its countersign status.
No rule row is countersigned yet.

Not legal advice, and not a docketing service of record. Local rules, a
case management order or a judge's standing order can move almost any of
these, and the server cannot see them. State holidays are not applied.

https://federalcourtdeadlines.com/mcp
errors@federalcourtdeadlines.com
