
Legal Text Mcp De
io.github.klein-businessPublished by GitHub account klein-businessv2.1.3Updated Oct 24, 2026
German federal & state legal texts (BGB, DSGVO, …) with canonical IDs and cite-grade provenance.
Overview
Local MCP server that gives an assistant cite-grade German and EU legal texts with canonical IDs and source provenance.
- What you can do
- List and inspect loaded laws with optional metadata filtering, and read a single law's metadata and norm summaries. Fetch individual norms and resolve structured citations without legal interpretation. Full-text search across normalised legal texts, optionally limited to specific codes. Retrieve source metadata, source limitations, corpus coverage and related-norm relationships. Load the corpus as read-only legal:// resources and run curated prompt workflows such as citation checking and GDPR review.
- When to use it
- Useful when an assistant must quote or cite German federal, Länder or EU legal texts (BGB, DSGVO and similar) with traceable sources, for example checking a citation or locating the relevant norm. Not intended for legal advice or interpretation.
- Requirements
- Runs as a local process via uvx or the OCI image, or as a hosted streamable-HTTP endpoint. Needs a normalised dataset directory (laws.json, norms.json, search-index.json) supplied through DATASET_PATH; the package and Docker image ship no legal text, and no verified public corpus download is available. ANTHROPIC_API_KEY is optional and only used by the research_topic tool, which falls back to ranked search without it.
Installation
In SourceWeft
- Open Legal Text Mcp De in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[legal-text-mcp-de: German legal text MCP server banner]
[PyPI version] [Python 3.12 / 3.13] [License: Apache 2.0] [GitHub release] [Container image] [Docs]
[CI] [CodeQL] [OpenSSF Scorecard] [OpenSSF Best Practices] [SLSA Level 3] [Signed by cosign] [MCP Registry]
legal-text-mcp-de
Cite-grade German legal-text infrastructure for LLM agents. ~8 500 federal + Länder + EU laws via MCP, HTTP API, and a typer shell CLI — all over the same runtime, with cryptographic provenance from gesetze-im-internet.de and EUR-Lex / Cellar.
It is local or server-side infrastructure: no SaaS, no billing, no
accounts, no tenant model, and no legal advice. The runtime loads
either the committed fixture packages used by fast CI or a generated
production corpus package built outside Git. Official text comes from
gesetze-im-internet.de for German federal laws and from EUR-Lex /
Cellar for EU acts such as the GDPR.
No legal advice. This software returns text and structured metadata. It does not interpret the law, advise on it, or produce any legal conclusion. The maintainer assumes no liability for use in legal decision-making contexts.
Older internal documentation has been archived under docs-legacy/summary.md.
Status
Features
- MCP tools for listing laws, fetching norms, resolving citations, full-text search, and source provenance.
- HTTP API (FastAPI) over the same runtime, with structured
/health,/ready,/laws,/search, and OpenAPI endpoints. - Provenance-first design: every law and norm carries source URL, fetch timestamp, content hash, and the parser path it traversed.
- Two corpus modes: committed fixture packages for deterministic tests and CI, or a generated production package built from official sources at runtime.
- No editorial bundling: this repository ships tooling, not legal text. Texts are loaded from official sources at runtime.
Installation
pip or uvx with an explicit dataset
- The package and standard Docker image contain the runtime only.
DATASET_PATHmust point to a normalized dataset directory withlaws.json,norms.json, andsearch-index.json.- Public corpus OCI references and the
-fullimage currently returnDENIED; there is no verified public corpus download. - The CLI and HTTP runtime do not automatically prepare a usable dataset. A
.tar.zstbundle is not a supported direct runtime path. - Build the nine registered federal laws from official sources using the federal corpus guide. This requires the current source checkout and includes a fix beyond v2.1.3.
prepare_data.build_corpus --sources bundis not implemented. Its archive output is separate from the serving dataset format.
Docker with a mounted dataset
- Use a dataset compatible with the selected runtime version.
/healthchecks the process;/readychecks whether the HTTP API can serve its dataset.- For freshly built federal data, follow the guide's source-image build instructions.
Mode 5 — Public-hosted service
CLI
legal-text-mcp-de ships a full subcommand CLI. Bare invocation prints
--help. Common commands:
Place --json or --output yaml before the subcommand for machine-readable
output; the data field contains the HTTP response shape. See CLI reference for
the full subcommand list.
BREAKING in v2.1.0: bare
legal-text-mcp-denow prints--help. Appendserveto keep the v2.0 behaviour (started the MCP server).
Quickstart
MCP-client compatibility
- Tested requires a recorded client version, transport, successful
tools/list, and one successful tool call. - Configuration examples alone are not test evidence. Client runs below remain [UNVERIFIED]; protocol-level CI does not establish desktop-client compatibility.
Run the MCP server with the committed fixture corpus
The default transport is streamable HTTP at
http://localhost:8001/mcp. The CLI does not expose stdio; see
stdio transport status.
Dev shortcut. A
Justfilewraps the commonuvinvocations (just install,just test,just lint,just run,just api,just docs). Install viabrew install just. The Justfile is optional — CI only usesuvdirectly.
Run the HTTP API
Since v2.1 the easiest way is the new CLI:
The default port is 8001 (from settings.port / PORT env var); use
--port <N> to override.
Or directly via uvicorn (equivalent — same FastAPI app):
The HTTP layer enforces MAX_REQUEST_BODY_BYTES (default 1048576 = 1 MiB)
as a defence-in-depth body-size cap; over-limit requests return 413 Payload Too Large. The operator's reverse proxy is still expected to
enforce a proxy-level limit on top of this.
Docker
The Docker image does not bundle legal text data. Mount a validated
package at /data/legal-texts:
- See
examples/docker-compose/http/for a minimal HTTP-mode Compose example. - See
examples/docker-compose/production/for a committed, CI-tested production stack (MCP + HTTP behind Caddy, switchable via Compose profiles).
MCP Resources
Since v2.0, the corpus is exposed as read-only legal:// URIs that any MCP client can load directly into its LLM context. Examples:
legal://laws— paginated indexlegal://laws/bgb— BGB header + norm indexlegal://laws/bgb/norms/par:433— § 433 BGB as Markdownlegal://corpus/coverage— what's in the corpus
See docs/concepts/mcp-native.md for the full URI catalogue.
MCP Prompts (slash-commands)
Five curated workflows appear as slash-commands in MCP clients:
Smart Tools
research_topic is a multi-step research tool that orchestrates 2 LLM-sampling calls per invocation:
- Corpus search for candidate norms
- LLM ranking of candidates by relevance
- Related-norms graph loading
- LLM synthesis of a structured research report
When the client lacks sampling support, the tool returns a degraded report with ranked candidates only.
Data Sources
No text from these sources is committed to this repository. The generated-corpus pipeline fetches them at build time and stores provenance in a manifest.
MCP Tools
See the MCP tools reference for the full surface. Highlights:
list_laws(query?)— list loaded laws with optional metadata filter.get_law(code)— law metadata + normalised norm summaries.get_norm(code, norm)— return one structured norm.search_laws(query, codes?)— search normalised texts.resolve_citation(...)— resolve structured citations without legal interpretation.get_source_metadata(code?),get_source_limitations(...),get_corpus_coverage(),get_related_norms(code, norm).
MCP tools return JSON-compatible objects. They do not return double-serialised JSON strings.
HTTP API
Article-plus-section paths must be URL-encoded:
Documentation
Full documentation is published at klein-business.github.io/legal-text-mcp-de.
Quick links:
- Quickstart
- MCP tools
- HTTP API
- Operations: security, SBOM, cosign-verify, versioning, threat model
- Roadmap
Source-of-truth documents live in the repo: README.md, CHANGELOG.md, SECURITY.md, CONTRIBUTING.md, GOVERNANCE.md, NOTICE, LICENSE.
Development
The full fixture-backed release gate:
The public-flip readiness gate:
A Justfile wraps the common targets (just test,
just lint, just docs, just run, just api) for convenience.
Contributing
See CONTRIBUTING.md for guidelines, code of conduct, and security policy.
All contributions must comply with the Developer Certificate of Origin
(sign-off with git commit -s).
Verification
Every release since v1.0.0 is signed and accompanied by an SBOM and
SLSA-3 provenance. Examples below use v2.1.3; substitute the tag
you actually pulled.
Cosign image signature
See Verify with cosign for SBOM and SLSA attestation verification.
Licence and acknowledgements
This project is licensed under the Apache License 2.0. See NOTICE for required attribution.
Derived from floleuerer/deutsche-gesetze-mcp (Copyright (c) 2025 Florian Leuerer, MIT). Upstream licence terms are preserved in licenses/MIT-floleuerer.txt.
MCP Registry: io.github.klein-business/legal-text-mcp-de ·
registry.modelcontextprotocol.io
mcp-name: io.github.klein-business/legal-text-mcp-de
Source: README.md at commit 7f55963
Tools
0Version history
1- v2.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts