@pipeworx/de-gesetze

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/de-gesetze’s. Install: one-click buttons

Connect to just the @pipeworx/de-gesetze pack

https://gateway.pipeworx.io/de-gesetze/mcp — only @pipeworx/de-gesetze’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

German federal statutes and ordinances (Bundesrecht) — search by title or official abbreviation, read a single § or Art. in full, browse a law’s structure, and get its amendment status (“Stand”).

Tools

  • gesetze_search(query, limit?) — find a law by title keyword or abbreviation (“BGB”, “Datenschutz”). An abbreviation match returns that one law directly; otherwise ranks law titles by word overlap.
  • gesetze_law_info(law) — amendment metadata (“Stand”) for one law: official abbreviation/title, date of promulgation, official publication citation, the amendment-status entries (Neufassung/Stand), and the entry-into-force date when the source publishes one.
  • gesetze_structure(law, section_id?, depth?, provision_limit?) — the law’s table of contents (Buch/Abschnitt/Titel/Kapitel) with its §/Art. provisions listed under each heading. Paged: a branch with more provisions than provision_limit reports has_more_provisions rather than truncating silently.
  • gesetze_provision(law, provision) — full text of one § (Paragraph) or Art. (Artikel), by abbreviation and number (“823”, ”§ 823”, “823a”, “Art 1”), with its title and its own amendment/application footnote when the source attaches one.

Auth

Keyless.

Data sources

  • Bundesministerium der Justiz (BMJ) / juris GmbH, Gesetze im Internet — the federal government’s official collection of German statutes and ordinances currently in force, each as structured XML with its own amendment metadata.

Notes

  • Abbreviation matching. The collection’s own table of contents carries no separate abbreviation field — only a title and a per-law identifier. For the large majority of entries that identifier IS the law’s lowercase official abbreviation (the publisher’s own convention: bgb -> BGB, stgb -> StGB, estg -> EStG), and gesetze_search/gesetze_law_info/ gesetze_structure/gesetze_provision all resolve on that basis first. This is a documented convention, not a guarantee for every one of the ~6,100 entries — an obscure ordinance’s identifier occasionally departs from its cited abbreviation, in which case gesetze_search’s title search is the way in.
  • Per-law fetch is live, per call. Only the catalog (title + law identifier, ~6,100 entries) is baked into a lookup index; a law’s full text, structure and amendment metadata are fetched and parsed live on each call to gesetze_law_info/gesetze_structure/gesetze_provision — proxied, never mirrored. A short per-isolate cache avoids re-fetching the same law repeatedly in a burst of calls; it is not a persistent copy.
  • § vs. Art. Most laws number their provisions ”§ N”; a handful (constitutional and some international-treaty texts, e.g. the Grundgesetz) use “Art N” instead. gesetze_provision matches on the bare number/letter token, so either symbol works regardless of which one a given law actually uses — you do not need to know in advance.
  • Granularity. A provision is one § or Art. (the source’s own unit). Absätze (paragraphs) and Sätze (sentences) within a provision are part of its text, not separately addressable — consistent with how the publisher itself structures the document.
  • Copyright. German federal legislative and administrative texts are “amtliche Werke” and are not protected by copyright (§ 5 Urheberrechtsgesetz).
  • Index refresh. scripts/bake-de-gesetze-index.mjs regenerates src/de-index-data.ts from one live call to the publisher’s table of contents; it is registered in workers/gateway/src/pack-baked-indexes.json so it ships to KV, never into the gateway bundle.

Tools

  • gesetze_search — Search German federal statutes and ordinances (Gesetze im Internet, BMJ/juris) BY TITLE OR ABBREVIATION — “BGB”, “StGB”, “Datenschutz”, “Straßenverkehr”. An exact or near abbreviation match (BGB, StGB
  • gesetze_law_info — Amendment metadata (“Stand”) for a German federal law or ordinance: official abbreviation and title, date of promulgation (Ausfertigungsdatum), official publication citation (Fundstelle), the official
  • gesetze_structure — Table of contents of a German federal law or ordinance (Bücher/Abschnitte/Titel/Kapitel) with the §/Art. provisions listed under each heading, from Gesetze im Internet. depth controls how many headi
  • gesetze_provision — Full text of a single § (Paragraph) or Art. (Artikel) of a German federal law or ordinance, by abbreviation and provision number, from Gesetze im Internet. Accepts natural forms: “823”, ”§ 823”, “823a

Tools

  • gesetze_law_info — Amendment metadata ( Stand ) for a German federal law or ordinance: official abbreviation and title, date of promulgation (Ausfertigungsdatum), official publication citation (Fundstelle), the official
  • gesetze_provision — Full text of a single § (Paragraph) or Art. (Artikel) of a German federal law or ordinance, by abbreviation and provision number, from Gesetze im Internet. Accepts natural forms: 823 , § 823 , 823a ,
  • gesetze_search — Search German federal statutes and ordinances (Gesetze im Internet, BMJ/juris) BY TITLE OR ABBREVIATION — BGB , StGB , Datenschutz , Straßenverkehr . An exact or near abbreviation match (BGB, StGB, HG
  • gesetze_structure — Table of contents of a German federal law or ordinance (Bücher/Abschnitte/Titel/Kapitel) with the §/Art. provisions listed under each heading, from Gesetze im Internet. `depth` controls how many headi

Regenerated from source · build October 16, 2026