The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Prawo Pl MCP listing page.
One MCP server for Polish legal data.
Ten independent connectors - case law, legislation, the company register, tax rulings, public procurement, data-protection decisions, plus EU extras - behind four tools. Each connector stays a separate package with its own repository; this server spawns them on demand and translates between their conventions.
"Prawo" is Polish for "law"; the name follows yargi-mcp's move of naming a country server in its own language.
The connectors cover Polish legal data well, but as separate MCP servers, one per database - ten installs and ten config entries before the first question. yargi-mcp showed the fix for Turkish law: 16 institutions, one server. prawo-pl-mcp does the same for Poland:
pl_list_sources, pl_search, pl_get_document,
pl_call - fewer tool schemas means less context spent before the LLM starts
working.dateFrom here, date_from
there, pages counted from 0 or from 1 depending on the repo. Here page is
always 1-based and dates are always date_from/date_to (YYYY-MM-DD); the
translation happens inside. One name per concept applies to the aggregator's
own tools too: page is the page parameter of both pl_search and
pl_get_document (page_number still works as a deprecated alias), and
pl_call takes arguments or its alias args.native_params - the
native parameter name each unified one maps to for that source, so
article_number (eu-compliance) is visible without spawning the connector or
reading an upstream error. pl_call checks the names it was given against
the connector's own schema and says which one it meant.npx -y / uvx,
downloaded on the first call to a given source and kept alive afterwards.
A source that cannot start reports a readable error while the rest keep
working.isap) get the
page forwarded natively and are reported as pagination: "native" - the
aggregator does not re-cut an already-cut page and does not invent a
total_pages it cannot know.| Source id | What | Institution / database | Connector | Runtime |
|---|---|---|---|---|
saos | Case law: common courts, Supreme Court, Constitutional Tribunal + citator | SAOS | mcp-saos | npx |
nsa | Case law: administrative courts (NSA + 16 WSA) | CBOSA | mcp-nsa | npx |
isap | Legislation: Dziennik Ustaw + Monitor Polski, 96k+ acts | Sejm ELI API | mcp-isap | npx |
krs | Company register: extracts, history, board composition | KRS API (Ministry of Justice) | mcp-krs | npx |
eureka | Tax rulings: 550k+ individual interpretations | EUREKA (Ministry of Finance) | mcp-eureka | npx |
kio | Public procurement: National Appeal Chamber rulings | orzeczenia.uzp.gov.pl | kio-orzeczenia-mcp | uvx |
uodo | GDPR enforcement: Polish DPA decisions, fines, stats | orzeczenia.uodo.gov.pl | uodo-orzeczenia-mcp | uvx |
eu-sparql | EU law: EUR-Lex by CELEX, CJEU by ECLI, GDPRhub | Cellar SPARQL | mcp-eu-sparql | npx |
eu-compliance | 14 EU regulations offline (GDPR, AI Act, DORA, NIS2...) | Local SQLite corpus | mcp-eu-compliance | npx |
legalize | Law-as-git: 32 jurisdictions, versioned by commit | legalize-dev | legalize-mcp | uvx |
Polish sources are tagged group: pl, EU extras group: eu - filter with
pl_list_sources(group="pl").
| Tool | What it does |
|---|---|
pl_list_sources | Catalog of sources (no subprocess spawned). With source_id: live tool schemas of one connector. |
pl_search | Search any source with normalized parameters; source-specific filters via extra. |
pl_get_document | Full document by identifier (judgment id, ELI, KRS number, signature...), paginated. |
pl_call | Any native tool of any connector: citator, DPA statistics, board composition, regulation comparison... |
pl_coverage | Declare what this connector covers, when each family was captured, and - explicitly - what it does NOT cover. Every gap carries a fallback. |
The typical flow an LLM follows (spelled out in the server's instructions):
pl_list_sources → pl_search → pl_get_document, with pl_call for the
specialized tools each connector brings.
Requires Python ≥ 3.11 plus the runtimes of the sources you use: Node.js ≥ 18
for npx sources, uv for uvx sources. If a
runtime is missing, its sources report source_unavailable and the rest work.
Open by default (public, read-only data). Set PRAWO_PL_MCP_API_KEY to require
X-API-Key: <key> or Authorization: Bearer <key> on every request.
| Env | Default | Meaning |
|---|---|---|
PRAWO_PL_MCP_CMD_<ID> | - | Override the spawn command for a source, e.g. PRAWO_PL_MCP_CMD_SAOS="node C:/dev/mcp-saos/dist/index.js" for a local checkout. <ID> = source id, uppercase, - → _. |
PRAWO_PL_MCP_INIT_TIMEOUT | 180 | Seconds allowed for a connector's first start (includes package download). |
PRAWO_PL_MCP_TIMEOUT | 90 | Seconds per tool call after startup. |
PRAWO_PL_MCP_AUDIT_DIR | ~/.matematic/audit | Where the JSONL audit log goes. |
PRAWO_PL_MCP_API_KEY | - | ASGI mode only: require this API key (dual-channel). |
The aggregator is a thin proxy (ADR 0001). Connectors are not imported, vendored or forked; the aggregator speaks MCP to them over stdio the same way any client would. The whole layer is a source registry (one dataclass entry per connector), a lazy subprocess pool, a parameter translator and a paginator. Adding a source means adding a registry entry.
Every call lands in a JSONL audit log (timestamp, tool, source, parameter hash, latency - never document content).
Apache-2.0. Individual connectors carry their own licenses (MIT or Apache-2.0), their own rate limits and their own terms toward upstream databases - the aggregator adds no caching and no transformation beyond pagination, so each connector's constraints apply unchanged.