Cz MCP Server

Most developer tooling work still happens through a UI a human drives. Cz MCP server moves it into the conversation instead. MCP server for Czech legislation (e-Sbirka SPARQL) with ELI and verifiable citations.

The short version

An MCP server for the Czech e-Sbirka legal database (e-sbirka.gov.cz), the official Collection of Laws (Sbirka zakonu), via its open-data SPARQL endpoint. It searches acts and fetches their full consolidated text, with verifiable citations.

The tools it exposes

The server publishes 3 tools. What each one is for:

• cz_search — Find acts by year and/or a citation substring (discovery)
• cz_get_act — Metadata for an act by year + number, plus the latest consolidated version date
• cz_get_text — Full consolidated text of an act, assembled from the latest version's fragments

Getting it running

The server ships on PyPI as cz-eli-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cz's toolset — cz_search, cz_get_act, cz_get_text — is a fair guide to whether it matches your workflow. It is maintained by matematicsolutions; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.