Boutique · Connectors
45 MCP connectors (open-source, GitHub) to public sources of law - statutes, case law, the company register, the compliance corpus. Three continents: Europe (Poland, the EU, Switzerland, the UK and more), the Americas (Brazil, USA, Colombia, Chile, Canada) and Asia-Pacific (Japan, Singapore, Malaysia, Australia, Israel, Pakistan). Each gives the agent the source itself, with a stable identifier and a link back to it. Growing country by country, by ROI.
Open-source · Local · Public sources · One command or a config
ProblemBoutique is past 100 building blocks: connectors, skills, curated cards. An agent cannot tell which one solves its task, and a hosted search API sees every query by definition.
What it doesThe whole Boutique catalog as a local MCP connector: the agent searches it on your machine and gets the block's card with an install command (uvx/npx). A copy of the catalog lives on disk, so it works offline and query content never leaves the computer. When coverage is missing, the tool drafts a request - a human submits it.
uvx boutique-mcpsource · Apache-2.0 ↗ProblemItaly is the EU's largest legal market (~240k lawyers), yet Normattiva has no open API - the statute book lives in a portal and format out of the agent's reach.
What it doesA connector to the official Normattiva: statutes and codes as Akoma Ntoso with an ELI and URN identifier, a single article (e.g. art. 2043 of the Civil Code) and point-in-time text (multivigenza). Plus Constitutional Court (Corte Costituzionale) case law since 1956 with native ECLI. And it_verify_citations - it mechanically checks Italian statute citations in an AI answer: a made-up article gets caught, with a range hint (art. 9999 does not exist, the act has 51 articles). Each with a source link. The seventeenth EU connector in the eu-legal-mcp line.
uvx italy-eli-mcpsource · Apache-2.0 ↗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 ↗ProblemTurkish law - statutes, decree-laws, regulations - sits in the Ministry of Justice's system, keyless but unsearchable without a connector.
What it doesA connector to the keyless Bedesten API (Ministry of Justice): search by legislation type, full text and a table of contents, with a link to mevzuat.gov.tr. No case law - the top courts' portals were unreachable from this network or have no API.
uvx tr-eli-mcpsource · Apache-2.0 ↗ProblemUK law - Acts of Parliament plus Scottish, Welsh and Northern Irish instruments - sits out of the agent's reach without a dedicated connector.
What it doesA connector to legislation.gov.uk (The National Archives, keyless): Acts of Parliament, statutory instruments, and their Scottish, Welsh and Northern Irish equivalents with a persistent identifier. Plus case law via Find Case Law. As of v0.3.0, the GOV.UK Search API adds eight non-court document types in one query: employment tribunal decisions (132K), HMRC manual sections (85K), residential property tribunal decisions (17K), CMA cases and more - roughly 243K additional documents. Data under the Open Government Licence v3.0.
uvx gb-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 ↗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 ↗ProblemYou want the full text of French codes and statutes locally, with no PISTE account and no cloud calls - so a citation can be checked on the spot.
What it doesAn offline corpus of French law (full Legifrance/DILA text in a local SQLite FTS5 store, verbatim, zero-LLM): 193k provisions from the codes and LEGI statutes, a fail-closed citation-exists check, and a Legifrance link on every article. No key, drop-in - it complements fr-eli-mcp, which runs live via PISTE and covers case law.
npx -y @matematicsolutions/mcp-fr-legalsource · MIT ↗ProblemPolish legal sources sit in separate connectors: civil and administrative case law, legislation, the company register, tax rulings, public procurement, data-protection decisions. Seven connectors mean seven installs and seven config entries before the first question.
What it doesOne MCP server over the whole Polish shelf, plus three EU sources: four tools instead of forty-two. The connectors stay separate packages - the aggregator starts one only when a question needs it and translates between their parameter names, because every database counts pages its own way. Long judgments and statutes come back in 5,000-character pages, so one document does not fill the context window.
uvx prawo-pl-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: 537k rulings (common courts, Supreme Court, Constitutional Tribunal, KIO) - full text, docket number and source link on every one. Plus a citator, saos_cite_check - it checks whether a ruling is still good law: whether later judgments depart from its view and whether an enlarged-panel resolution exists, using 11 verified phrases that flag a break in the case line. With an explicit caveat that SAOS does not hold 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): 2.39M administrative rulings with a docket number and source link.
npx -y @matematicsolutions/mcp-nsasource · MIT ↗Problem517k individual KIS rulings decide the tax consequences of a transaction, yet they sit in EUREKA behind a search UI no agent can drive.
What it doesA connector to the public EUREKA API (eureka.mf.gov.pl): full-text search of KIS rulings by content and case number, the complete text, issue date and a source link on every document.
npx -y @matematicsolutions/mcp-eurekasource · 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.2.1).
uvx kio-orzeczenia-mcpsource · Apache-2.0 ↗ProblemRomanian law (Portal Legislativ) is available through a SOAP API - out of the agent's reach without a connector.
What it doesA connector to Romania's Portal Legislativ (legislatie.just.ro): full act text by number, year and type, with a stable identifier and a source link. The fifteenth EU connector in the eu-legal-mcp line.
uvx ro-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 ↗ProblemBelgium's official gazette publishes in French, Dutch and German - without a connector the agent can't reach any of them.
What it doesA connector to ejustice.just.fgov.be: acts by coordinate (type/year/month/day/NUMAC number) or a year browse, trilingual (French by default), with a source link. No full-text search - lookup is by coordinate only.
uvx be-eli-mcpsource · Apache-2.0 ↗ProblemHungarian law (NJT) lives in a portal with no search API - out of the agent's reach without a connector.
What it doesA connector to the official Nemzeti Jogszabalytar - Hungary has had a native ELI identifier since 2023: acts by coordinate (type/year/issuer/serial), full text and a list of issuers, with a source link.
uvx hu-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 ↗ProblemCzech consolidated law (e-Sbirka) is served over SPARQL/RDF - rich, but out of the agent's reach without a connector.
What it doesA connector to the open e-Sbirka SPARQL endpoint (opendata.eselpoint.gov.cz): Czech legislation with a national ELI identifier and a source link. The line's first SPARQL connector. The eleventh EU connector in the eu-legal-mcp line.
uvx cz-eli-mcpsource · Apache-2.0 ↗ProblemSwiss federal law sits outside the EU, but a Polish lawyer on a cross-border matter still needs to reach it - impossible without a connector.
What it doesA connector to Fedlex (SPARQL, keyless) - the only non-EU connector in the whole fleet with a genuinely NATIVE ELI identifier (the same jolux ontology as Luxembourg's Legilux), multilingual DE/FR/IT/EN, with a source link. The Swiss citation is the SR number (Systematische Sammlung).
uvx ch-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 ↗ProblemDanish legislation lives in Retsinformation as LexDania XML - a rich format, but out of the agent's reach without a connector.
What it doesA connector to the keyless, Open Data Retsinformation (retsinformation.dk): Danish law as LexDania XML behind native ELI identifiers, with a source link. The tenth EU connector in the eu-legal-mcp line.
uvx dk-eli-mcpsource · Apache-2.0 ↗ProblemSlovak consolidated law (Slov-Lex) lives in a portal whose text the agent can't reach without a connector.
What it doesA connector to the static Slov-Lex mirror (static.slov-lex.sk): Slovak legislation by year/number with a national ELI identifier, consolidated versions and a source link. The fourteenth EU connector in the eu-legal-mcp line.
uvx sk-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 ↗ProblemCroatian legislation (Narodne novine) is published with European ELI in JSON-LD - out of the agent's reach without a connector.
What it doesA connector to Narodne novine (nn.hr): Croatian legislation with a European ELI identifier (data.europa.eu) and a source link. The twelfth EU connector in the eu-legal-mcp line.
uvx hr-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 ↗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 ↗ProblemLithuanian legal acts (TAR) sit in open data behind the Spinta API - the agent can't search them without a connector.
What it doesA connector to Lithuania's Register of Legal Acts (TAR) via data.gov.lt (Spinta): consolidated acts with full text, a stable identifier and a source link. The thirteenth EU connector in the eu-legal-mcp line.
uvx lt-eli-mcpsource · Apache-2.0 ↗ProblemMaltese law (Legislation.mt) is published with ELI and full text as PDF - out of the agent's reach without a connector.
What it doesA connector to Malta's Legislation.mt: metadata with a national ELI identifier and full text from the official PDF, with a source link. The sixteenth EU connector in the eu-legal-mcp line.
uvx mt-eli-mcpsource · Apache-2.0 ↗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): ~4M EU legal acts and CJEU rulings, each with a stable identifier and source link.
npx -y @matematicsolutions/mcp-eu-sparqlsource · MIT ↗Problem14 EU regulations across digital, data and cyber (GDPR, the AI Act, DORA, NIS2, DSA, DMA, Data Act, CRA and more) - 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.
npx -y @matematicsolutions/mcp-eu-compliancesource · MIT ↗ProblemThe statute books of 32 countries live in separate portals and formats - out of the agent's reach without a connector for each one.
What it doesOne server covers legislation for 32 jurisdictions (21 EU) from the legalize-dev corpus: each law as a Markdown file with an ELI-style identifier, a reform history (every change is a commit) and a link to the official source. Keyless, local. Our layer over the open MIT corpus - one server instead of a connector per country.
uvx legalize-mcpsource · Apache-2.0 ↗ProblemBrazil is the single largest legal market in the world (roughly 1.3M OAB-registered lawyers), yet tracking a bill's progress or getting a verifiable citation to an enacted law meant searching separate portals by hand.
What it doesEight keyless APIs in one package. Legislative process (Camara dos Deputados), URN Lex for enacted laws with full article text (Senado + normas.leg.br), case status via DataJud CNJ (STJ/TST/TSE/TRF/TJ/TRT/TRE). Four sources now return real ruling full text, not just metadata: STJ (Brazil's second-highest court, from May 2022), CARF (tax rulings), TST (labor supreme court - 3.75M acordaos, 8.48M documents) and TCU (Federal Court of Accounts - 525K acordaos in procurement cases).
uvx br-eli-mcpsource · Apache-2.0 ↗ProblemThe US legal market counts over 1.37M active lawyers (ABA, 2025), yet tracking a bill through Congress means searching Congress.gov by hand.
What it doesFive sources, ten read-only tools. Congressional legislative process (Congress.gov), full enacted-law text as GovInfo packages (U.S. Code, Statutes at Large, annual CFR editions, Federal Register), full-text search over the Federal Register (1M+ documents since 1994, including 8,513 presidential documents) and the current CFR (413K sections with amendment history). As of v0.3.0, case law via CourtListener - 8.29M opinions in full text, with the headline value in state case law (California, New York, Texas), which no federal source covers. For heavy federal case-law work, the mature MIT-licensed CourtListener wrappers remain the recommendation - this connector's strength is the states.
uvx us-eli-mcpsource · Apache-2.0 ↗ProblemColombia has one of the highest lawyer-to-population ratios in the world (roughly 801 per 100k), yet confirming a Constitutional Court ruling exists - and who the reporting justice was - means searching the portal by hand.
What it doesA connector to the open datos.gov.co dataset (Socrata): search and fetch Corte Constitucional sentencias by docket ("T-153/26"), with a source link. Metadata only - no full text in the source.
uvx co-eli-mcpsource · Apache-2.0 ↗ProblemChilean law (LeyChile) publishes its data in an open RDF/OWL ontology - a rarity in the region - but it's unsearchable without a connector.
What it doesA connector to the National Congress Library's SPARQL endpoint (BCN, keyless): search and fetch norms (statutes, decrees, regulations) by BCN resource identifier, with a source link. Metadata only, no full text.
uvx cl-eli-mcpsource · Apache-2.0 ↗ProblemCanadian federal law (over 136k lawyers per the FLSC) is bilingual and spread across codes - without a connector the agent can't reach the right version.
What it doesA connector to the official Justice Laws Website: metadata and full XML text for federal Acts and regulations by code (e.g. "C-46"), bilingual EN/FR, with a source link. No full-text search (you need the act's code) and no case law - CanLII's ToS bars bulk redistribution.
uvx ca-eli-mcpsource · Apache-2.0 ↗ProblemJapanese law - statutes, cabinet orders, ministerial ordinances - is available through an official API, but unsearchable without a connector.
What it doesA connector to the keyless REST/JSON e-Gov API (Japan's Digital Agency) - the only connector in the whole fleet with native JSON, not XML/Akoma Ntoso: keyword search, a single article and full text (truncated for very large statutes), with a source link.
uvx jp-eli-mcpsource · Apache-2.0 ↗ProblemSingapore Statutes Online (SSO) offers no search - its robots.txt disallows the search path - so without a connector the agent can only browse by hand.
What it doesA connector to Singapore Statutes Online: browse acts (no full-text search, respecting the robots.txt restriction), a single provision and full text, with a source link. The fleet's first connector with a genuine HTML parser.
uvx sg-eli-mcpsource · Apache-2.0 ↗ProblemMalaysia's principal Acts are published as PDF only, with no search API - out of the agent's reach without a connector.
What it doesA connector to Laws of Malaysia Online (Attorney-General's Chambers): fetch an act by number and full text extracted from the official PDF, with a source link. MVP covers principal Acts only - amendments and subsidiary legislation are out of scope.
uvx my-eli-mcpsource · Apache-2.0 ↗ProblemAustralia's federal statute book has no open search API in ELI format - unsearchable without a connector.
What it doesA connector to the official Federal Register of Legislation: search Acts and full text from genuine server-side rendering, with an FRLI identifier (e.g. "C2004A00042") and a source link. MVP covers Acts - regulations and other instrument types are out of scope.
uvx au-eli-mcpsource · Apache-2.0 ↗ProblemIsraeli law (Knesset statutes) is available through a rich official OData API, but unsearchable without a connector.
What it doesA connector to the official Knesset OData API (the KNS_IsraelLaw entity): full-text search of law names in Hebrew, in-force status and a Basic Law flag, with a source link. It also serves the published law versions (including consolidated texts) with the official PDFs straight from the Knesset's server, plus a local case-law index (10,558 judgments from family, district, labor and administrative courts, a HuggingFace dataset) - the dataset's license is undocumented, so this data is not for further redistribution.
uvx il-eli-mcpsource · Apache-2.0 ↗ProblemPakistan publishes no machine-readable legal API - the official portal is readable only by eye, so an agent can reach neither the statutes nor the judgments.
What it doesA corpus-based connector: 967 federal statutes (full text from the official pakistancode.gov.pk PDFs, as of January 2025) and 1,414 Supreme Court judgments (full text, as of July 2024), with full-text search. Every response carries a citation and a source link, and the connector states how current it is itself - honest, no pretending to be current law.
uvx pk-eli-mcpsource · Apache-2.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. The whole fleet is on package registries (PyPI/npm) - the command is on each card. Don't want to paste everything? boutique-mcp alone is enough: the agent finds and points to the rest.
{
"mcpServers": {
"boutique-mcp": { "command": "uvx", "args": ["boutique-mcp"] },
"prawo-pl-mcp": { "command": "uvx", "args": ["prawo-pl-mcp"] },
"at-eli-mcp": { "command": "uvx", "args": ["at-eli-mcp"] },
"au-eli-mcp": { "command": "uvx", "args": ["au-eli-mcp"] },
"be-eli-mcp": { "command": "uvx", "args": ["be-eli-mcp"] },
"br-eli-mcp": { "command": "uvx", "args": ["br-eli-mcp"] },
"ca-eli-mcp": { "command": "uvx", "args": ["ca-eli-mcp"] },
"ch-eli-mcp": { "command": "uvx", "args": ["ch-eli-mcp"] },
"cl-eli-mcp": { "command": "uvx", "args": ["cl-eli-mcp"] },
"co-eli-mcp": { "command": "uvx", "args": ["co-eli-mcp"] },
"cz-eli-mcp": { "command": "uvx", "args": ["cz-eli-mcp"] },
"de-eli-mcp": { "command": "uvx", "args": ["de-eli-mcp"] },
"dk-eli-mcp": { "command": "uvx", "args": ["dk-eli-mcp"] },
"es-eli-mcp": { "command": "uvx", "args": ["es-eli-mcp"] },
"fi-eli-mcp": { "command": "uvx", "args": ["fi-eli-mcp"] },
"fr-eli-mcp": { "command": "uvx", "args": ["fr-eli-mcp"], "env": { "PISTE_CLIENT_ID": "", "PISTE_CLIENT_SECRET": "" } },
"gb-eli-mcp": { "command": "uvx", "args": ["gb-eli-mcp"] },
"hr-eli-mcp": { "command": "uvx", "args": ["hr-eli-mcp"] },
"hu-eli-mcp": { "command": "uvx", "args": ["hu-eli-mcp"] },
"ie-eli-mcp": { "command": "uvx", "args": ["ie-eli-mcp"] },
"il-eli-mcp": { "command": "uvx", "args": ["il-eli-mcp"] },
"it-eli-mcp": { "command": "uvx", "args": ["italy-eli-mcp"] },
"jp-eli-mcp": { "command": "uvx", "args": ["jp-eli-mcp"] },
"kio-orzeczenia-mcp": { "command": "uvx", "args": ["kio-orzeczenia-mcp"] },
"legalize-mcp": { "command": "uvx", "args": ["legalize-mcp"] },
"lt-eli-mcp": { "command": "uvx", "args": ["lt-eli-mcp"] },
"lu-eli-mcp": { "command": "uvx", "args": ["lu-eli-mcp"] },
"mcp-eu-compliance": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-eu-compliance"] },
"mcp-eu-sparql": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-eu-sparql"] },
"mcp-eureka": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-eureka"] },
"mcp-fr-legal": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-fr-legal"] },
"mcp-isap": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-isap"] },
"mcp-krs": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-krs"] },
"mcp-nsa": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-nsa"] },
"mcp-saos": { "command": "npx", "args": ["-y", "@matematicsolutions/mcp-saos"] },
"mt-eli-mcp": { "command": "uvx", "args": ["mt-eli-mcp"] },
"my-eli-mcp": { "command": "uvx", "args": ["my-eli-mcp"] },
"nl-eli-mcp": { "command": "uvx", "args": ["nl-eli-mcp"] },
"pk-eli-mcp": { "command": "uvx", "args": ["pk-eli-mcp"] },
"ro-eli-mcp": { "command": "uvx", "args": ["ro-eli-mcp"] },
"se-eli-mcp": { "command": "uvx", "args": ["se-eli-mcp"] },
"sg-eli-mcp": { "command": "uvx", "args": ["sg-eli-mcp"] },
"sk-eli-mcp": { "command": "uvx", "args": ["sk-eli-mcp"] },
"tr-eli-mcp": { "command": "uvx", "args": ["tr-eli-mcp"] },
"us-eli-mcp": { "command": "uvx", "args": ["us-eli-mcp"] }
}
}
Connectors are MCP servers, not skills - you connect them with one command (uvx or npx), by cloning the repository ("GitHub only" tag) 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, or only gives metadata without full text, the connector says so plainly - it never fakes currency or completeness.
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.