Tools

Seven tools covering EU legal research — document discovery, content retrieval, citation resolution, case law, relationship graph traversal, EuroVoc thesaurus lookup, and raw SPARQL access:

eurlex_search_documents

Search EU legislation, treaties, preparatory acts, and more across the 2.7M+ work CELLAR corpus.

• Keyword search across work titles and CELEX string patterns
• Filter by document category (REG, DIR, DEC, TREATY, and more), with each category expanding to its reviewed CELLAR authority family
• Optionally include consolidated texts whose basic act belongs to the selected category
• Date range filtering (date_from, date_to)
• EuroVoc concept filtering — use eurlex_browse_subjects first to resolve concept IDs
• Filter to in-force acts only
• Pagination via offset and configurable limit (max 100)
• Returns CELEX numbers, work URIs, document types, and dates for chaining into eurlex_get_document

eurlex_get_document

Fetch the notice and full text of an EU legal act.

• Accepts CELEX numbers (e.g., 32016R0679), ELI URIs, or CELLAR work URIs
• Returns structured metadata: title, date, document type, author institution, legal basis, EuroVoc subjects, in-force flag
• Full text in HTML (default), Markdown, or Formex4 XML — format: "markdown" converts the act body to clean Markdown server-side (recitals and numbered points as readable text, genuine data tables as GFM)
• Content shaping for large acts: ordinary offset-based "paged" windows and "full" windows are capped at 100,000 characters; content_mode "paged" (default) returns the requested character window (offset + limit), while "full" returns the first window from offset zero. Both include content_chars_total, content_offset, content_chars_returned, and has_more, so repeated paged calls can reconstruct the complete body without loss; "metadata_only" skips the body, while structural outline/selection behavior is unchanged
• Navigate structure instead of raw offsets: outline: true returns the act's chapters, articles, annexes, and recitals as a heading list (each with its character offset), and select (e.g. { articles: "1,5,17" }) returns just those sections' text — degrading cleanly to the paging floor for acts with no detectable structure (e.g. case law)
• Supports the 24 EUR-Lex language codes case-insensitively, normalizes them to uppercase, defaults to English, and automatically falls back to English when a requested translation is unavailable
• Preserves the exact shaped body in structured output; HTML and XML are shown literally in the text response inside a source-safe tilde fence, while Markdown remains rendered Markdown
• Older acts and some CJEU judgments may lack English translations

eurlex_lookup_celex

Resolve EU legal identifiers to canonical CELLAR works.

• Accepts CELEX numbers and ELI URIs
• Auto-detects format with identifier_type: "auto" (default); set explicitly when auto-detection fails
• Returns work URI, confirmed CELEX number, document type, and date — the prerequisite step before eurlex_get_document or eurlex_get_relations

eurlex_get_cases

Search CJEU and General Court case law.

• Case-specific search: case number, keyword, court (CJEU or GC), and case type (judgment, order, ag_opinion)
• Date range filtering
• Primary records only by default — derivative information notices, abstracts, and summaries are excluded; set include_derivative to include them
• Returns case identifier, court, date, document type, and parties
• Distinct from eurlex_search_documents — case law (CELEX sector 6) has its own search parameters and practitioner workflows

eurlex_get_relations

Traverse the CELLAR relationship graph for a given work.

• Amendment chain (what amends it, what it amends)
• Consolidated versions (the current in-force text)
• Legal basis
• Citation network (cdm:work_cites_work in both directions)
• National transposition measures
• Filter to specific relation types or retrieve all at once
• Returns one-hop relations; multi-hop traversal requires multiple calls or eurlex_query_sparql

eurlex_browse_subjects

Resolve human-readable terms to EuroVoc concept IDs.

• Full-text search across the multilingual EuroVoc thesaurus
• Returns concept URI, preferred label, concept code, and broader/narrower hierarchy hints
• Supports all EU official languages; defaults to English
• Required before using the eurovoc_concept filter in eurlex_search_documents

Resources and prompts

All resource data is also reachable via tools. Resources provide stable-URI injectable context for agents that support MCP resources.

Features

Built on @cyanheads/mcp-ts-core:

• Declarative tool, resource, and prompt definitions — single file per primitive, framework handles registration and validation
• Unified error handling — handlers throw, framework catches, classifies, and formats
• Pluggable auth: none, jwt, oauth
• Swappable storage backends: in-memory, filesystem, Supabase, Cloudflare KV/R2/D1
• Structured logging with optional OpenTelemetry tracing
• STDIO and Streamable HTTP transports
• MCP 2026-07-28 support, exact tool-input validation, and structured error envelopes clients can act on

EUR-Lex-specific: