English Français العربية

Docket Alarm

Official registry Government and legal

Docket Alarm MCP — state + county + federal court dockets (docketalarm.com)

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http docket-alarm 'https://gateway.pipeworx.io/docket-alarm/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "docket-alarm": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/docket-alarm/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-docket-alarm
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-docket-alarm

Docket Alarm MCP — state + county + federal court dockets (docketalarm.com)

Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
docketalarm_searchSearch court dockets (state + federal) for <query> — full-text search across 675M+ US state, county, and federal court dockets (deeper state coverage than CourtListener). Returns matching cases with court, docket number, title, filing date, and link. Example: docketalarm_search({ q: "patent infringement Apple", limit: 20, _apiKey: "user@example.com:yourpassword" })
docketalarm_get_docketGet full docket detail for a case — returns case title, parties, filing date, and docket entries for a specific court + docket number. Cached documents are free. Example: docketalarm_get_docket({ court: "U.S. District Court, N.D. California", docket: "5:11-cv-01846", _apiKey: "user@example.com:yourpassword" })
docketalarm_search_pacerSearch federal PACER dockets by party — live party-name search across federal PACER (Appellate, Bankruptcy, Civil, Criminal, MDL). Note: this passes live PACER search fees at cost. Returns matching federal cases with court, docket, title, and filing date. Example: docketalarm_search_pacer({ party_name: "Microsoft Corporation", _apiKey: "user@example.com:yourpassword" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "docket-alarm": {
      "url": "https://gateway.pipeworx.io/docket-alarm/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/docket-alarm/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1878+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/docketalarm_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "docket-alarm": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-docket-alarm"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-docket-alarm

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Docket Alarm data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Frequently asked questions

What is Docket Alarm?

Docket Alarm MCP — state + county + federal court dockets (docketalarm.com)

How do I install Docket Alarm?

It runs as a remote server. In Claude Code: claude mcp add --transport http docket-alarm 'https://gateway.pipeworx.io/docket-alarm/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Docket Alarm need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Docket Alarm open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Docket Alarm?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.