fjc_court_codes

Pack: fjc-case-outcomes · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/fjc_court_codes for the schema, then POST the same URL with its arguments for the data.

Find the Federal Judicial Center (FJC) Integrated Database numeric code for a federal district court or circuit by name, e.g. “Eastern District of Texas” returns district code 40, “Fifth Circuit” returns circuit code 5. Accepts a full name, a Bluebook form (“E.D. Tex.”), a PACER-style short form (“txed”) or a state name (returns every district in that state); give kind “district”, “circuit” or “all” with no query to list every court of that kind (94 districts, 12 circuits). An unrecognised name returns the nearest matches, never an empty result. The codes are the ones the other FJC tools take as district_or_circuit (they also accept names directly). Source: FJC Integrated Database codebooks. Keyless.

Parameters

NameTypeRequiredDescription
querystringyesCourt name, abbreviation, state or code, e.g. “Eastern District of Texas”, “E.D. Tex.”, “Texas”, “Ninth Circuit”. Omit it and pass kind to list courts.
kindstringnoRestrict to district courts or circuits; with no query, “all” lists every court.

Example call

Arguments

{
  "query": "Eastern District of Texas"
}

curl

curl -X POST https://gateway.pipeworx.io/fjc-case-outcomes/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fjc_court_codes","arguments":{"query":"Eastern District of Texas"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('fjc_court_codes', {
  "query": "Eastern District of Texas"
});

More examples

{
  "kind": "circuit"
}

Response shape

FieldTypeDescription
publisherstringPublisher of the code lists
sourcestringDataset the codes come from
querystring | nullThe query asked, null when listing
matchedstringexact, nearest or all
countnumberCourts returned
courtsarrayMatching courts
notestringSet when the result is the nearest matches
errorstringSet when neither query nor kind was given
Full JSON Schema
{
  "type": "object",
  "properties": {
    "publisher": {
      "type": "string",
      "description": "Publisher of the code lists"
    },
    "source": {
      "type": "string",
      "description": "Dataset the codes come from"
    },
    "query": {
      "type": [
        "string",
        "null"
      ],
      "description": "The query asked, null when listing"
    },
    "matched": {
      "type": "string",
      "description": "exact, nearest or all"
    },
    "count": {
      "type": "number",
      "description": "Courts returned"
    },
    "courts": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "code": {
            "type": "string",
            "description": "FJC code as stored"
          },
          "name": {
            "type": "string",
            "description": "Publisher label"
          },
          "kind": {
            "type": "string",
            "description": "district or circuit"
          },
          "long_name": {
            "type": "string",
            "description": "Full court name"
          }
        },
        "additionalProperties": true
      },
      "description": "Matching courts"
    },
    "note": {
      "type": "string",
      "description": "Set when the result is the nearest matches"
    },
    "error": {
      "type": "string",
      "description": "Set when neither query nor kind was given"
    }
  },
  "additionalProperties": true
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the fjc-case-outcomes pack
{
  "mcpServers": {
    "fjc-case-outcomes": {
      "url": "https://gateway.pipeworx.io/fjc-case-outcomes/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build November 18, 2026