Court Listener vs Entscheidsuche — Schw… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Court Listener vs Entscheidsuche — Schweizer Gerichtsentscheide
In-depth architectural comparison of the Court Listener and Entscheidsuche — Schweizer Gerichtsentscheide MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Court Listener
Legal · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Entscheidsuche — Schweizer Gerichtsentscheide
Legal · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Court Listener if you need specialized Legal tools running via a local process. Choose Entscheidsuche — Schweizer Gerichtsentscheide if your workspace requires Legal integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Court Listener when:
You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You know what the case is **called** — "Roe v. Wade", or just "Sullivan"
lookup_citation
You have a reporter citation — "410 U.S. 113"
list_case_opinions
You have a case and want its majority, concurrences and dissents
get_opinion
You have an opinion id and want the **full text
search_opinions
Case search by name, judge or category (mirror-first; a specific `court` code searches live)
search_dockets
Docket-level search, upstream
list_docket_filings
You have a `docket_id` and want the **docket sheet** — what was filed, when
get_docket_filing
You have a `document_id` and want that one filing + its PDF
search_court_filings
You want the **text of filings** — motions, briefs, orders — not opinions
Entscheidsuche — Schweizer Gerichtsentscheide Tools (6)
search
Volltextsuche mit Lucene-Syntax. Filter nach Entscheiddatum, Scrape-Datum, Hierarchie (Kanton / Gericht / Kammer) und Sprache. Sortierung nach Relevanz, Entscheiddatum oder Scrape-Datum. Paginierung über `next_cursor` / `search_after`. Aggregationen für Facetten-Auswertung.
search_by_case_number
Exakte Phrasensuche nach Geschäftsnummern, Aktenzeichen und BGE-Zitaten (z.B. `BGE 142 III 1`, `6B_1234/2025`, `5A_396/2015`). Setzt die Nummer automatisch in Anführungszeichen.
fetch_document
Vollständigen Entscheid samt Volltext anhand der ID abrufen.
list_hierarchy
Hierarchie-IDs (Bund / Kanton / Gericht / Kammer) mit Trefferzahlen.
list_facets
Hierarchischer Facetten-Baum mit lokalisierten Labels in DE/FR/IT.
server_info
Versions- und Konfigurationsinformationen.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Court Listener is categorized under Legal and uses a local stdio subprocess. In contrast, Entscheidsuche — Schweizer Gerichtsentscheide belongs to Legal using remote streaming HTTP/SSE transport. Select Court Listener when you need capabilities focused on legal and Entscheidsuche — Schweizer Gerichtsentscheide when you require tools for legal.