SAOS MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SAOS MCP Find recent Polish court judgments on software contract disputes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SAOS MCP - Polish Court Judgments
An MCP server that connects Claude (and other AI clients) to SAOS - the official public database of Polish court judgments (System Orzecznictwa Sądów Powszechnych i Sądu Najwyższego).
Who is this for? Polish lawyers, legal researchers, and law students who want to search and analyze Polish court decisions directly inside Claude, Cursor, or any MCP-compatible AI client. No API key required - SAOS is a public database.
Features
Full-text search across hundreds of thousands of Polish judgments from courts of appeal, regional courts, and district courts
Filter by case number, judge name, court type, judgment type, and date range
Retrieve full judgments - metadata, operative part (sentencja), and complete reasoning (uzasadnienie)
Local file archive - in stdio mode, saves each retrieved judgment as a
.mdfile for offline referenceIn-memory cache (15 min TTL) to avoid redundant API calls
Timeout protection - 15-second abort signal on all API requests
Dual transport - stdio for local Claude Desktop use, HTTP for remote/hosted deployment
Related MCP server: Entscheidsuche MCP Server
Dla polskich prawników
SAOS MCP pozwala Claude'owi przeszukiwać bazę orzeczeń sądowych i analizować je bezpośrednio w rozmowie. Nie musisz otwierać przeglądarki ani kopiować tekstów — wystarczy zapytać Claude'a.
Jak zacząć
Krok 1. Zainstaluj Node.js (wersja 20 lub nowsza). To jedyna techniczna rzecz do zrobienia.
Krok 2. Otwórz plik konfiguracyjny Claude Desktop:
Windows: naciśnij
Win + R, wpisz%APPDATA%\Claudei otwórz plikclaude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Krok 3. Dodaj poniższy wpis do sekcji mcpServers (jeśli plik jest pusty, wklej całość):
{
"mcpServers": {
"SAOS": {
"command": "npx",
"args": ["-y", "@thescalablelegalmarketer/saos-mcp"]
}
}
}Krok 4. Zapisz plik i zrestartuj Claude Desktop. Przy pierwszym uruchomieniu Claude automatycznie pobierze serwer.
Przykładowe zapytania
Znajdź w SAOS 3 orzeczenia z lat 2020-2025 dotyczące sporów
o nienależyte wykonanie umowy wdrożeniowej oprogramowania.
Dla każdego podaj:
- sentencję (dosłowny cytat)
- podstawę prawną
- główny argument sąduWyszukaj orzeczenia dotyczące praw autorskich do oprogramowania
stworzonego przez pracownika na rzecz pracodawcy. Jakie stanowisko
zajmowały sądy w kwestii własności kodu?Uwaga: Orzeczenia w bazie SAOS mają zanonimizowane dane stron (zamiast nazwisk widnieje
(...)). To cecha samej bazy danych, nie ograniczenie narzędzia.
Installation
Claude Desktop (recommended)
Prerequisites: Node.js 20+ must be installed on your machine.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"SAOS": {
"command": "npx",
"args": ["-y", "@thescalablelegalmarketer/saos-mcp"]
}
}
}Restart Claude Desktop. The server starts automatically - no separate process needed.
Config file location:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Remote HTTP (self-hosted)
{
"mcpServers": {
"SAOS": {
"url": "https://your-domain.com/mcp"
}
}
}See Deployment for instructions on hosting your own instance.
From source (development)
git clone https://github.com/pawelojdowski/saos-mcp
cd saos-mcp
npm install
npm run build{
"mcpServers": {
"SAOS": {
"command": "node",
"args": ["C:\\PATH\\TO\\saos-mcp\\dist\\index.js"]
}
}
}Environment variable (stdio mode only):
SAOS_OUTPUT_DIR- directory for saved.mdjudgment files (default:~/Documents/saos-orzeczenia)
Tools
saos_search_judgments
Search for judgments in the SAOS database. Results sorted by date (newest first). All parameters optional.
Parameter | Type | Description |
| string | Full-text search across all fields (content + metadata) |
| string | Exact case number, e.g. |
| string | Judge's full name |
| string | SAOS thematic keyword, e.g. |
| string |
|
| string |
|
| string | Format |
| string | Format |
| number | Max 20, default 10 |
| number | Starting from 0 |
Tip: SAOS full-text search requires all keywords to appear in the text. Use multiple specific terms rather than quoted phrases, e.g. umowa wdrożeniowa oprogramowanie nienależyte wykonanie.
saos_get_judgment
Retrieve a full judgment by ID. Returns metadata, verbatim operative part (sentencja), and full reasoning (uzasadnienie). In stdio mode, also saves a .md file to SAOS_OUTPUT_DIR.
Parameter | Type | Description |
| number | Required. Judgment ID from |
saos_list_courts
Returns a list of common courts (ID, name, type). Use this to find court IDs for filtering.
Example prompt
Use SAOS to find 3 judgments from 2024–2025 concerning disputes over
defective implementation of ERP software contracts.
For each judgment call saos_get_judgment and provide:
1. Operative part - quote verbatim from the [VERBATIM QUOTE] section
2. Ratio decidendi - summarize the main reason for the ruling from the
"Sąd zważył" section of the reasoning
3. Legal basis - which provisions did the court invokeDevelopment
npm run dev # stdio server (TypeScript, no build needed)
npm run dev:http # HTTP server on port 3000
npm run build # type-check + esbuild bundle → dist/
npm run start # run compiled stdio bundle
npm run start:http # run compiled HTTP serverDeployment
Build and run with Docker:
docker build -t saos-mcp .
docker run -p 3000:3000 saos-mcpMCP endpoint: http://localhost:3000/mcp
Health check: http://localhost:3000/health
Deploy to Railway, Render, or Fly.io using the included Dockerfile.
Project structure
saos-mcp/
├── src/
│ ├── types.ts ← SAOS API TypeScript interfaces
│ ├── api.ts ← SAOS API client + in-memory cache
│ ├── format.ts ← HTML parsing, text formatting, file saving
│ ├── server.ts ← createMcpServer() factory - tool registration
│ ├── index.ts ← stdio entry point
│ └── http-server.ts ← HTTP entry point + /health endpoint
├── dist/ ← build output (gitignored)
│ ├── index.js ← stdio bundle (with #!/usr/bin/env node shebang)
│ └── http-server.js ← HTTP bundle
├── build.mjs ← esbuild config (two outputs in parallel)
├── tsconfig.json ← type-check only (noEmit), bundling via esbuild
├── server.json ← MCP marketplace manifest
├── Dockerfile ← multi-stage build → image with http-server.js
├── icon.svg
└── package.jsonKnown limitations
Partial coverage - SAOS indexes mainly courts of appeal and regional courts; district courts are less complete
Anonymized parties - the API returns
(...)instead of party names; this is a feature of the SAOS databasedecisionfield - available mainly for Supreme Court judgments; for common courts the operative part is extracted via HTML parsingIn-memory cache - 15 min TTL, resets on process restart
HTTP mode - does not save
.mdfiles (no access to the user's file system)
About SAOS
SAOS (System Analizy Orzeczeń Sądowych - System of Analysis of Court Judgments) is an open academic project led by the Interdisciplinary Centre for Mathematical and Computational Modelling (ICM) at the University of Warsaw, funded by the National Centre for Research and Development (grant IS-1/040/NCBR/2014).
The platform aggregates judgments from Polish common courts, administrative courts, the Supreme Court (Sąd Najwyższy), the Constitutional Tribunal (Trybunał Konstytucyjny), and the National Appeals Chamber (KIO). Data is imported automatically from official court portals. Personal data appearing in judgments is processed under GDPR Art. 6(1)(e) (public interest); responsibility for its publication rests with the source court systems.
The API is freely accessible with no authentication required.
Disclaimer: This tool is intended for legal research only and is not a substitute for professional legal advice. Always verify citations against primary sources before relying on them in legal proceedings.
License
Apache-2.0 © Paweł Ojdowski
Available Tools
3 toolssaos_get_judgmentA
Pobiera pełne orzeczenie z SAOS po ID. Zwraca metadane + sentencję dosłownie + pełne uzasadnienie. W trybie lokalnym zapisuje też plik .md z kopią archiwalną.
Inputs: id (required).
saos_list_courtsA
Zwraca listę sądów powszechnych (ID, nazwa, typ). Użyj żeby znaleźć ID sądu do filtrowania w saos_search_judgments.
Inputs: no named parameters.
saos_search_judgmentsA
Wyszukuje orzeczenia sądowe w bazie SAOS (sortowanie: najnowsze pierwsze).
ZASADA NACZELNA — frazy prawne zawsze w cudzysłowie: • query: "umowa o dzieło" → szuka tej dokładnej frazy (wysokа precyzja) • query: umowa o dzieło (bez cudzysłowu) → AND po słowach osobno = fałszywe trafienia
STRATEGIA — stosuj warstwowo:
Główne pojęcie w cudzysłowie: "umowa o dzieło", "rękojmia za wady", "bezpodstawne wzbogacenie"
Dodaj keyword= z hasłem tematycznym SAOS — to kuratorowana taksonomia niezależna od treści, np. keyword: "umowa o dzieło"
Połączenie query + keyword daje najlepszą precyzję
Dodaj judgmentType=SENTENCE gdy szukasz wyroków merytorycznych (nie postanowień)
PRZYKŁADY: • query: "umowa o dzieło" "wynagrodzenie", judgmentType: SENTENCE • query: "nienależyte wykonanie", keyword: "umowa o dzieło" • query: "odstąpienie od umowy" "wada", ccCourtType: APPEAL • caseNumber: "VIII GC 23/24" → konkretna sygnatura
Jeśli wyniki są nieistotne: dodaj cudzysłowy, dołącz keyword, zawęź typ sądu lub daty.
Inputs: query, dateTo, keyword, dateFrom, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: searching judgments, fetching a specific judgment by ID, and listing courts. There is no overlap or ambiguity between them.
All tool names follow a consistent pattern: saos_ + verb + noun (search_judgments, get_judgment, list_courts). This makes the API predictable and easy to navigate.
With only 3 tools, the server is tightly scoped to its purpose of accessing court judgments. This is an appropriate size for a focused legal database, avoiding unnecessary complexity.
The tool set covers the complete workflow: find courts for filtering, search for judgments with rich query options, and retrieve full details for a specific judgment. There are no obvious gaps for typical use cases.
Related MCP Connectors
Polish legal data for AI assistants: full-text search across 2.94M+ court rulings (common courts, Supreme Court, Constitutional Tribunal, KIO, NSA/WSA), statute text and version history from the official ELI register (164k+ acts), rulings citing a provision and citations between rulings, a citation verifier for case numbers, case-outcome and duration statistics, KIS tax interpretations, CJEU rulings applied in Poland, UODO decisions, KRS company lookup, court competence, official bank accounts and legal calculators. Works without an API key (daily limit).
Semantic search over Polish law and case law, citing the exact in-force article.
Polish statutes (Dziennik Ustaw, ELI) and court rulings (SAOS) for AI agents. Runs on Apify.
Polish and EU law: statutes, rulings, UODO/UOKiK/KNF, EU regulations, citation checks. Free tier.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI-powered legal research and analysis of Polish legal acts from the Sejm API. Provides comprehensive search, document retrieval, metadata analysis, and content access for legal documents from Dziennik Ustaw and Monitor Polski.1323MIT
- AlicenseNot gradedqualityNot gradedmaintenanceProvides access to Swiss court decisions through the entscheidsuche.ch API, enabling search, retrieval, and analysis of legal documents across different cantons and courts using natural language queries.-
- AlicenseNot gradedqualityFmaintenanceEnables querying and analyzing Slovak legislation via natural language, including full-text search, provision retrieval, and EU law integration.63 npm2Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for Polish case-law (SAOS) — Supreme Court, Constitutional Tribunal, common courts and KIO — with ECLI and verifiable citations.3134 npm2MIT