Eu Cellar MCP server

@pipeworx/eu-cellar

Every document the Publications Office of the European Union has issued — Official Journal acts, treaties, consolidated texts, COM proposals and Court of Justice judgments — searchable by title and readable by CELEX number, from the CELLAR semantic repository's public SPARQL endpoint.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

title search across every EU resource type; returns CELEX, date, resource type and a direct EUR-Lex link.

• cellarsearchworks(query, resource_type?, since?, until?, limit?) — full-text

English title, document date, in-force flag, resource types, EuroVoc subject concepts with English labels, authoring bodies.

• cellarwork(celex? | cellarid?) — one document's catalogue entry: every

Writes are refused; results are capped.

• cellar_sparql(query, limit?) — your own SELECT or ASK against the repository.

Auth

Keyless. No registration, no key, no published quota.

Relationship to the eur-lex pack

Both talk to publications.europa.eu and they are not duplicates. eur-lex is a curated legal-compliance surface: a hand-kept index of ~14 named acts (GDPR, AI Act, DORA…), article-level text extraction and CJEU judgment lookup, with its SPARQL use hard-wired to legislation. This pack is the repository itself — all resource types, plus an arbitrary SELECT-only query tool.

Use eur-lex for "what does GDPR Article 17 say". Use this for "what has the EU published about X" and for graph questions nobody wrote a tool for.

Data sources

endpoint (Virtuoso), serving the Common Data Model (cdm:) graph.

• — the CELLAR SPARQL

endpoint returns.

• — the Work URIs the

Traps, all verified live 2026-09-17

is Virtuoso; a CONTAINS filter over ?title scans every expression in the repository and times out. The full-text form is ?title bif:contains "'phrase'" — note the INNER single quotes, which Virtuoso requires for a multi-word phrase.

• Full text needs bif:contains, not FILTER(CONTAINS(...)). The endpoint

matches nothing; it needs ^^xsd:string. This is a clean HTTP 200 with zero rows, not an error.

• CELEX literals are typed. ?w cdm:resourcelegalid_celex "32024R1689"

lang(?title) = "en" silently drops a large share of the repository. Filter on the expression's language URI instead — that is the modelled fact.

• Titles come back both with and without a language tag. Filtering on

product means a single document legitimately comes back as 20 bindings. cellar_work collapses them; hand-written SPARQL will not.

• One Work returns many rows. The (title × type × subject × author) cross

inconsistently and you can get RDF/XML where you asked for JSON.

• format= is a query parameter. The Accept header alone is honoured

reads as "no results". This pack raises it as a rejected query.

• A malformed query is HTTP 200 with an HTML error page. Parsed naively that

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "eu-cellar": {
      "url": "https://gateway.pipeworx.io/eu-cellar/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/eu-cellar/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.