Legal Docket Monitor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXCEL_ITEM_ID | No | Excel item ID (required if CLIENT_SOURCE_TYPE=excel). | |
| EXCEL_DRIVE_ID | No | Excel drive ID (required if CLIENT_SOURCE_TYPE=excel). | |
| GRAPH_CLIENT_ID | No | Azure AD client ID for Graph authentication (required for sharepoint/excel). | |
| GRAPH_TENANT_ID | No | Azure AD tenant ID for Graph authentication (required for sharepoint/excel). | |
| EXCEL_TABLE_NAME | No | Excel table name (required if CLIENT_SOURCE_TYPE=excel). | |
| WEBHOOK_BASE_URL | No | Base URL for custom webhook backend (required if CLIENT_SOURCE_TYPE=webhook). | |
| CLIENT_SOURCE_TYPE | No | Optional. One of: sharepoint, excel, webhook. Enables client-matching tools. | |
| SHAREPOINT_LIST_ID | No | SharePoint list ID (required if CLIENT_SOURCE_TYPE=sharepoint). | |
| SHAREPOINT_SITE_ID | No | SharePoint site ID (required if CLIENT_SOURCE_TYPE=sharepoint). | |
| WEBHOOK_AUTH_TOKEN | No | Authorization token for webhook backend (required if CLIENT_SOURCE_TYPE=webhook). | |
| GRAPH_CLIENT_SECRET | No | Azure AD client secret for Graph authentication (required for sharepoint/excel). | |
| COURTLISTENER_API_TOKEN | No | Your CourtListener API token. Required for all modes. | |
| WEBHOOK_SEARCH_FALLBACK | No | Optional boolean string (true/false) for webhook fallback behavior. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docketsA | Search CourtListener for federal court dockets by case name, party name, or docket number. Returns a list of matching cases with IDs you can use in other tools. |
| get_docketB | Fetch full metadata for a specific CourtListener docket by its numeric ID. Returns case name, docket number, court, judge, filing dates, and status. |
| get_new_filingsA | Get docket entries (filings) for a case, optionally filtered to entries since a given date. Use this to check what has been filed since you last looked at a case. |
| get_docket_summaryA | Get a combined summary of a docket: key metadata plus the most recent N filings. Ideal for a quick status check on a matter. |
| get_partiesC | Get the parties and their attorneys for a docket. |
| watch_docketA | Add a docket to the watch list. Use check_watched_dockets to poll all watched dockets for updates. |
| unwatch_docketB | Remove a docket from the watch list. |
| list_watched_docketsA | List all dockets currently on the watch list. |
| check_watched_docketsA | Poll all watched dockets for new filings since they were last checked. Updates the last-checked timestamp for each docket after polling. When triage is enabled, each new filing is classified by urgency via the connected model (sampling) — routine, needs-review, or urgent. |
| find_matching_clientsA | Fuzzy-search the firm's configured client list (SharePoint, Excel, or custom webhook) for clients matching a name or query. Requires CLIENT_SOURCE_TYPE to be configured. Use this to find candidate clients before linking a docket with link_docket_to_client. |
| link_docket_to_clientA | Link a docket to a client in the firm's client list. If the case name matches a single client with high confidence, links automatically. If multiple clients are plausible matches, asks the user to confirm via an interactive prompt (elicitation) rather than guessing. Requires CLIENT_SOURCE_TYPE to be configured. |
| check_client_sourceA | Health check the configured client list backend (SharePoint, Excel, or webhook). Useful when setting up a new connection to verify credentials and connectivity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose, from health checks to client linking to docket retrieval and watch list management. No two tools overlap in functionality; descriptions are precise and disambiguate effectively.
All tool names follow a consistent verb_noun pattern using lowercase with underscores, e.g., check_client_source, get_docket, link_docket_to_client. The naming is predictable and aids in understanding tool roles.
12 tools is well-scoped for a legal docket monitoring server, covering search, retrieval, watch list management, client linking, and health checks with no unnecessary clutter.
The tool surface provides comprehensive coverage for monitoring court dockets: searching, fetching metadata, filings, parties, managing a watch list, linking to clients, and verifying connectivity. There are no obvious gaps for the stated purpose.