{
  "markdown": "# EUR-Lex — EU legislation and Court of Justice case law\n\nThe Regulations and Directives themselves, article by article, plus the\njudgments interpreting them.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Auth\n\nNone. Everything here is keyless.\n\n## Two halves\n\n**Legislation** — `compliance_index`, `search_legislation`, `get_metadata`,\n`list_articles`, `get_article`, `get_document`. Named acts resolve by alias, so\n`get_article({celex: \"GDPR\", article: \"17\"})` returns the right to erasure\nwithout anyone knowing that GDPR is `32016R0679`.\n\n**Case law** — `cjeu_search`, `cjeu_judgment`. The Court of Justice and the\nGeneral Court.\n\n```\ncjeu_search({query: \"data protection\"})\n  → 62023CJ0097  Court of Justice  Judgment  2026-02-10\n    WhatsApp Ireland Ltd v European Data Protection Board\n\ncjeu_judgment({case_number: \"C-97/23\"})\n  → 87,178 characters of the Grand Chamber judgment\n```\n\n## Caveats worth passing on\n\n- **An Official Journal notice is not a judgment.** `62023CA0097` is a\n  paragraph-long summary of the ruling in `62023CJ0097`. Both match a title\n  search for the same case, so notices are excluded unless you pass\n  `include_notices: true`.\n- **A case number does not say what the court produced.** \"C-97/23\" might be a\n  judgment, an order, or an Advocate General's opinion. `cjeu_judgment` tries\n  them in that order, and if it ends up returning something other than the\n  judgment it sets `substituted: true` and says so — an AG's opinion is a\n  recommendation to the Court, not the Court's ruling.\n- **Old cases may have no English judgment.** English became an EU language in\n  1973, so for a 1964 case the judgment often has no English expression even\n  though a later-translated AG opinion does. That is the main way\n  `substituted` shows up in practice.\n- **Two-digit years mean what the court means.** `6/64` is 1964 and `97/23` is\n  2023; a two-digit year above the current one belongs to the last century.\n- **Search matches the title, not the full text.** CJEU titles name the parties\n  and the subject matter, which is usually enough — but a doctrine discussed\n  only in the reasoning will not be found by title.\n\n## Related\n\n- `us-code`, `court-listener` — the US equivalents, statutes and case law\n- `ted-eu` — EU public procurement notices\n\n## Data sources\n\n- EUR-Lex CELLAR (`publications.europa.eu`) — document text\n- EU Publications Office SPARQL endpoint — search over CELEX metadata\n\n© European Union, 1998–2026. Reuse authorised under the Commission's reuse\npolicy; EUR-Lex data is not covered by the Court's own copyright.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"eur-lex\": {\n      \"url\": \"https://gateway.pipeworx.io/eur-lex/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/eur-lex/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Eur Lex data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4661,
  "sha": "02e434045dee497aee6edd52d7a5f817cb0cec3785c9c14f59491d373c467777",
  "repo_slug": "pipeworx-io/mcp-eur-lex",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_eur_lex_5572ed42/readme"
}