Skip to main content
Glama
courtio

CourtAPI MCP Server

Official
by courtio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to CourtAPI MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-pacer

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables live searching of US federal court cases and parties across all federal district, bankruptcy, and appellate courts via the PACER Case Locator, using your PACER credentials.
      460 npm
      1
      MIT

    • courtlistener-mcp

      Vaquill-AI
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides AI assistants access to the CourtListener legal database (US court opinions, dockets, RECAP, PACER, oral arguments, judges) and the full eCFR federal regulations via the official CourtListener API v4. It supports bring-your-own-key authentication and is designed for use with MCP-compatible clients like Claude, VS Code, and Cursor.
      34
      4
      MIT

    • mcp-docket-alarm

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to search and retrieve court docket records across US state, county, and federal courts, including PACER party searches, and to get full case details.
      358 npm
      MIT

    • legal-mcp

      jscottym
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables US case law search, citation parsing, practice management via Clio, and federal court filings through PACER.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: case discovery, national search, court codes, case metadata, dockets, documents, claims, parties, creditor schedules, and PACER credentials. Descriptions explicitly differentiate similar tools such as get_creditors vs get_claims and ncl_search vs find_cases, so there is no ambiguity.

    Naming Consistency4/5

    Most tools consistently use the 'get_' prefix for retrieving known resources (get_case, get_dockets, get_document, get_claims, get_parties, get_creditors, get_pacer_credentials). However, three tools deviate: ncl_search, list_courts, and find_cases use different verb styles or acronyms, introducing minor inconsistency.

    Tool Count5/5

    With 10 tools, the server is well-scoped. Each tool covers a distinct aspect of court record access, from case finding to document retrieval to credential management, with no redundancy. This is an appropriate size for the domain.

    Completeness5/5

    The tool set covers the full workflow: discovering cases (find_cases, ncl_search), retrieving case metadata (get_case), dockets (get_dockets), documents (get_document), parties (get_parties), creditors (get_creditors), and claims (get_claims), plus court metadata (list_courts) and PACER credentials (get_pacer_credentials). No obvious gaps for a read-only court records API.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources