BGB (Germany)

German Civil Code (BGB) as executable rules: periods, deadlines and more, answered with grounds

OtherHTMLv0.1.9

arxo-bgb.git

Smithery

Pinned canon, executable as it stands: source text with provenance, the model built over it and the scenarios that check its answers. The norms here are data — they are executed by law; this repository carries no rule code of its own.

Contents

PackageVersionScenariosDependencies
calc.kinship0.1.0390
de.bgb.core0.1.010
doctrine.ius_privatum0.1.0370
de.bgb.fristen0.1.0861
de.bgb_18960.1.051
de.bgb.allgemeiner_teil0.1.0213
de.bgb.besitz_eigentum0.1.01432
de.bgb.betreuung0.1.01102
de.bgb.dienst_werk0.1.02102
de.bgb.ehe0.1.0573
de.bgb.ius_privatum0.1.013
de.bgb.miete0.1.0312
de.bgb.sonstige_vertraege0.1.04982
de.bgb.uebergang0.1.0152
de.bgb.dingliche_rechte0.1.01233
de.bgb.erbfolge0.1.0404
de.bgb.schuldrecht_at0.1.0514
de.bgb.verwandtschaft0.1.0824
de.bgb.bereicherung_delikt0.1.0715
de.bgb.kauf0.1.0905
de.bgb.verfuegungen0.1.0825

How it is verified

Every package is built by package.py with the pinned toolchain: compilation, §267 scenarios on both evaluators, replay of saved evaluations and a rebuild from the release itself. A failure of any step stops the build.

python3 tools/toolchain.py download --lock toolchain.lock.json --out /tmp/law-tools
python3 /tmp/law-tools/package.py packages/<name> \
    --lawc /tmp/law-tools/law-cli --offline --out /tmp/<name>-release

Dependencies

Dependency bytes are pinned under packages/<name>/deps/ and verified against the contentHash recorded in law.lock: the build and the CI are offline.

Asking these packages

Two ways, the same slice of the canon and the same engine; the difference is whose machine evaluates.

  • Hosted: https://mcp.arxo.io/mcp/de-bgb — requests are evaluated on Arxo infrastructure.
  • Local: docker compose -f mcp/compose.yml up — nothing leaves the machine.

mcp/pin.json records what either one must answer from: the content hash of the canon profile, the pinned packages, the ABI version of the engine and the availability of the hosted endpoint. An answer that cannot be traced to that pin is not this repository's answer.

Worked cases

Each collection is a case package of its own: the facts, the questions and the answers, with the pinned canon as its dependency. Ask one from its directory with law ask . — nothing is downloaded.

CollectionCasesQuestions
packages/de.bgb.fristen/examples/ein-fall-drei-kodizes64
packages/de.bgb.fristen/examples/fristenrechner816
packages/de.bgb_1896/examples/ein-fall-zwei-jahrhunderte56
packages/de.bgb.miete/examples/kuendigung-und-mieterhoehung614
packages/de.bgb.uebergang/examples/vor-und-nach-200249
packages/de.bgb.erbfolge/examples/erbfolge-und-pflichtteil818
packages/de.bgb.schuldrecht_at/examples/rechtsbehelfe66
packages/de.bgb.schuldrecht_at/examples/verzugszinsen59
packages/de.bgb.schuldrecht_at/examples/widerruf612

Rights

Code and model: see LICENSE. The pinned texts of the publishers keep their own terms of reproduction, listed per package in NOTICE; those terms are not covered by the code licence.

Maintainer: Rifat Dzhumagulov (hi@arxo.io). Address: git@github.com:arxohq/arxo-bgb.git.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @arxo/mcp-de-bgb

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-arxo-de-bgb": {
      "command": "npx",
      "args": [
        "-y",
        "@arxo/mcp-de-bgb"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@arxo/mcp-de-bgbnpm

Compatible MCP Clients

BGB (Germany) works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More