Boutique · Connectors
16 MCP connectors (open-source, GitHub) to public sources of EU and Polish law - statutes, case law, the company register, the compliance corpus. Each gives the agent the source itself, with a stable identifier and a link back to it. Ordered by reach: EU-wide first, then national law country by country; Poland's own bases come last.
Open-source · Local · Public sources · One command or a config
Each connector gives the agent the source itself, with a stable identifier and a link back to it. EU-wide sources first, then national law country by country - growing by ROI. Poland's own bases close the list.
Together the connectors reach no fewer than 4M source documents: the full EUR-Lex and CJEU corpus, 3.7M+ rulings in the Dutch Rechtspraak, the official gazettes of more EU countries - plus 96k acts in Poland's Journal of Laws (ISAP), 530k+ rulings in SAOS and the KRS company register. We count downward: there are more in reality.
ProblemEU law and CJEU case law are spread across EUR-Lex and the Cellar repository - precise lookup by hand is slow.
What it doesA connector to the EU Publications Office SPARQL (EUR-Lex / Cellar): EU legislation and CJEU rulings with a stable identifier.
npx -y @matematicsolutions/mcp-eu-sparqlsource · MIT ↗ProblemGDPR, the AI Act, DORA, NIS2, eIDAS 2.0, CRA - reaching the exact article while you work means hopping across PDFs.
What it doesAn offline corpus of EU law (full EUR-Lex text in local SQLite FTS5, verbatim, zero-LLM): the exact article at hand, with nothing for a model to invent.
ProblemGerman federal law sits on its own portal in its own format - a wall for cross-border work.
What it doesA connector to the official NeuRIS (rechtsinformationen.bund.de): federal legislation with ELI and case law with native ECLI, each with a source link. The first EU connector in the eu-legal-mcp line.
uvx de-eli-mcpsource · Apache-2.0 ↗ProblemFrench legislation and case law (Legifrance) sit behind the PISTE API - without a connector and credentials the agent can't reach them.
What it doesA connector to the Legifrance API via PISTE: legislation (LODA, codes) and case law (JURI) with native ECLI. Needs a free PISTE account (OAuth) - so it isn't drop-in like the others.
uvx fr-eli-mcpsource · Apache-2.0 ↗ProblemDutch consolidated law (BWB) needs the version in force on a given date - tedious to pin down by hand.
What it doesA connector to KOOP SRU (BWB) and Rechtspraak Open Data: acts in force on a chosen date and case law by native ECLI, each with a source link. 3.7M+ rulings in reach.
uvx nl-eli-mcpsource · Apache-2.0 ↗ProblemSpanish consolidated law lives in the BOE - a separate portal and format the agent usually can't reach.
What it doesA connector to the BOE open-data API (boe.es): consolidated legislation by id/ELI with a source link.
uvx es-eli-mcpsource · Apache-2.0 ↗ProblemAustrian federal law is another national database in its own format - a second wall for cross-border work.
What it doesA connector to the official RIS (data.bka.gv.at): federal legislation (Bundesrecht) with ELI and case law (Judikatur) with native ECLI, each with a source link.
uvx at-eli-mcpsource · Apache-2.0 ↗ProblemSwedish statutes (SFS) sit in the Riksdag's open data - without a connector the agent can't search them.
What it doesA connector to the Riksdag open-data API (SFS): consolidated acts with a persistent identifier and a source link.
uvx se-eli-mcpsource · Apache-2.0 ↗ProblemFinland's consolidated statutes sit in Finlex, in Akoma Ntoso format - out of the agent's reach without a connector.
What it doesA connector to the Finlex open-data API (opendata.finlex.fi): consolidated statutes with an ELI identifier and a source link.
uvx fi-eli-mcpsource · Apache-2.0 ↗ProblemIrish acts and statutory instruments sit in the Irish Statute Book - a separate collection the agent can't reach.
What it doesA connector to the Irish Statute Book (irishstatutebook.ie): acts and SIs by year/number with an ELI identifier and a source link.
uvx ie-eli-mcpsource · Apache-2.0 ↗ProblemLuxembourg law (Legilux) comes as jolux RDF and Akoma Ntoso - rich formats, but out of the agent's reach without a connector.
What it doesA connector to Legilux (data.legilux.public.lu): ELI-native jolux metadata and full Akoma Ntoso text, with a source link.
uvx lu-eli-mcpsource · Apache-2.0 ↗ProblemThe Journal of Laws and Monitor Polski run to hundreds of thousands of acts - finding the right version of a provision by hand eats your time.
What it doesA connector to the Sejm's ELI API: 96k acts since 1918, with a stable ELI identifier and a source link on every provision.
npx -y @matematicsolutions/mcp-isapsource · MIT ↗ProblemCommon-court and Supreme Court rulings are scattered across portals - you copy the docket number and lose the source.
What it doesA connector to the SAOS API: full judgment text, docket number and source link on every ruling.
npx -y @matematicsolutions/mcp-saossource · MIT ↗ProblemPolish GDPR, tax and administrative case law lives in CBOSA - a separate database the agent usually can't see.
What it doesA connector to CBOSA (NSA + 16 regional courts): administrative rulings with a docket number and source link.
npx -y @matematicsolutions/mcp-nsasource · MIT ↗ProblemCompany ties, boards, shareholders - reading KRS extracts by hand is slow and error-prone.
What it doesA connector to the Ministry of Justice's official, free KRS API: company-register data straight to the agent.
npx -y @matematicsolutions/mcp-krssource · MIT ↗ProblemNational Appeal Chamber rulings settle public-procurement disputes, but the UZP database is separate and awkward to search.
What it doesA connector to the public orzeczenia.uzp.gov.pl database: KIO rulings with a docket number and source link. Early prototype (v0.1.0).
Add it to the MCP config file in PATRON or Claude (the mcpServers key). Needs uvx (Python) and npx (Node). For France, fill in your PISTE credentials. KIO and EU-Compliance install from GitHub for now.
{
"mcpServers": {
"mcp-eu-sparql": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-eu-sparql"] },
"de-eli-mcp": { "command": "uvx", "args": ["de-eli-mcp"] },
"fr-eli-mcp": { "command": "uvx", "args": ["fr-eli-mcp"], "env": { "PISTE_CLIENT_ID": "", "PISTE_CLIENT_SECRET": "" } },
"nl-eli-mcp": { "command": "uvx", "args": ["nl-eli-mcp"] },
"es-eli-mcp": { "command": "uvx", "args": ["es-eli-mcp"] },
"at-eli-mcp": { "command": "uvx", "args": ["at-eli-mcp"] },
"se-eli-mcp": { "command": "uvx", "args": ["se-eli-mcp"] },
"fi-eli-mcp": { "command": "uvx", "args": ["fi-eli-mcp"] },
"ie-eli-mcp": { "command": "uvx", "args": ["ie-eli-mcp"] },
"lu-eli-mcp": { "command": "uvx", "args": ["lu-eli-mcp"] },
"mcp-isap": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-isap"] },
"mcp-saos": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-saos"] },
"mcp-nsa": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-nsa"] },
"mcp-krs": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-krs"] }
}
}Connectors are MCP servers, not skills - you connect them with one command (uvx or npx) or by pasting a ready-made config into PATRON or Claude, not through the wizard. The "source" link points to the open repository. Public sources, run locally; most are keyless - France (Legifrance/PISTE) needs free OAuth credentials. Open; licence and scope live in the repository. If a source is incomplete or changes, the connector says so plainly - it never fakes currency.
Connectors feed the agent its sources. When you need a ready procedure - reviewer, citation extraction, clause checklist - see the skills.
Connectors support a lawyer's work; they don't replace their judgement. MateMatic's reading of the GDPR and the AI Act, not the position of any bar or chamber.