@theyahia/casebook-mcp
by theYahia
README.md
# @theyahia/casebook-mcp
MCP server for **Casebook/Pravo.ru** -- Russian legal case search, court documents, participant lookup, judge statistics, and hearing schedules.
## Tools
| Tool | Description |
|------|-------------|
| `search_cases` | Search cases by query, INN, court, dates, type |
| `get_case` | Get case details and participants |
| `get_case_events` | Get hearing schedule and decisions |
| `search_participants` | Search participants by name or INN |
| `get_participant_cases` | Get all cases for a participant |
| `get_judge_stats` | Get judge case statistics |
| `get_court_info` | Get court information |
| `get_document` | Get court document by ID |
## Install
### Claude Desktop / Cline / Cursor
```json
{
"mcpServers": {
"casebook": {
"command": "npx",
"args": ["-y", "@theyahia/casebook-mcp"],
"env": { "CASEBOOK_TOKEN": "<YOUR_TOKEN>" }
}
}
}
```
### Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| `CASEBOOK_TOKEN` | Yes | API token from [Casebook](https://casebook.ru/) |
## Demo Prompts
- "Search for bankruptcy cases involving INN 7707083893"
- "Get details for case A40-12345/2026"
- "Show hearing schedule for case A40-12345/2026"
- "Find all cases where Sberbank is a participant"
- "Get case statistics for judge Ivanov"
- "Show court info for the Moscow Arbitration Court"
- "Get document doc-789 from case A40-12345/2026"
- "Search for contract dispute cases from 2025"
## API Reference
Casebook API documentation: [https://casebook.ru/](https://casebook.ru/)
## License
MIT
TDQS
A3.6/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct resource or aspect (case details, events, court info, documents, judge stats, participant cases, search). No overlap; all clearly differentiated by resource and query type.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern with verbs 'get' or 'search'. No mixing of styles or irregular naming.
Tool Count5/5
8 tools cover the core query operations for a court case system. The count is well-scoped without being excessive or insufficient.
Completeness4/5
Covers major query needs: cases, events, documents, courts, judges, participants. Minor gaps like listing all courts or judges are absent but not critical for typical read-only use.
Maintenance
ActivityInactive
ResponsivenessSyncing