MCP Fr Judilibre

What @pipeworx/mcp-fr-judilibre does

@pipeworx/mcp-fr-judilibre exposes Judilibre data from the Cour de cassation and the judicial courts covered by that service. It is intended for applications that need to find published French judicial decisions, inspect their pseudonymised text, and interpret the compact classification values returned by the source.

The search operation supports free-text queries and filters for jurisdiction, chamber, formation, decision type, theme, publication, solution, and date range. Results include decision identifiers, summaries, and highlighted passages. A separate decision lookup returns the complete text, structural zones represented as character offsets, cited texts, related decisions, and attached files.

How it works

The service can be used through a hosted streamable HTTP endpoint or through the npm package as a local stdio bridge. The local process forwards MCP requests to the Pipeworx gateway, so it needs an internet connection and does not provide an offline data store.

The gateway serves the Judilibre tools alongside shared Pipeworx meta-tools on the hosted pack endpoint. The npm bridge lists the pack tools by default and can expose the shared tools with PIPEWORX_META_TOOLS=1. The gateway also offers ask_pipeworx for asking questions in natural language instead of selecting a tool directly.

Judilibre access is backed by the state PISTE API gateway. Requests use an API key header rather than an OAuth bearer token for the upstream service. The hosted gateway manages that upstream access; the local bridge can use a Pipeworx account key sent as a bearer token.

Setup and configuration

A hosted MCP client can connect to:

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

For a local stdio connection, configure npx with the package name:

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

Anonymous local calls are capped at 50 per day. Setting PIPEWORX_API_KEY raises the allowance to 200 calls per day. The gateway also provides an HTTP tool interface, including a POST route for invoking fr_judilibre_search without an MCP client.

Tools and capabilities

• fr_judilibre_search searches the published open-data corpus with text, classification, and date filters.
• fr_judilibre_decision retrieves full decision text, structural offsets, citations, related decisions, and files.
• fr_judilibre_taxonomy translates source codes into French labels, performs reverse lookups, or lists taxonomy categories.
• Decision citations include visa entries and best-effort cited_articles links for chaining into the related France Légifrance article tool.

Citation parsing recognises specific article-reference forms found in Cour de cassation text. Other forms are marked as unparsed rather than being inferred.

Limitations and notes

Judilibre’s published corpus contains decisions selected for publication by the Cour de cassation; it is not a complete archive of every decision rendered. Returned data is read per request, with the response carrying the call’s data date.

The upstream service requires an application key and Judilibre API access through PISTE, including acceptance of the Judilibre terms for both sandbox and production. The data is offered under Licence Ouverte / Open Licence 2.0, alongside the PISTE terms and Judilibre-specific reuse terms. The package itself is licensed under MIT.