bogamatic-sac-mcp
# bogamatic-sac-mcp
MCP server for interacting with the Argentine judiciary system (SAC - Justicia Cordoba) via Claude Desktop.
## Installation
Requires [Claude Desktop](https://claude.ai/download) and [uv](https://docs.astral.sh/uv/getting-started/installation/).
Add to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"bogamatic-sac": {
"command": "uvx",
"args": ["--refresh", "bogamatic-sac-mcp"],
"env": {
"SAC_MATRICULA": "1-XXXXX",
"SAC_USERNAME": "tu usuario de login al SAC",
"SAC_PASSWORD": "tu contraseña del SAC"
}
}
}
}
```
### Variables de entorno
- `SAC_MATRICULA` — tu matrícula (formato `1-XXXXX`). Es la que identifica al abogado en el SAC y en la base de Bogamatic.
- `SAC_USERNAME` — tu usuario para ingresar al SAC. Puede ser tu matrícula, tu CUIT o un alias — depende de cómo te registraste.
- `SAC_PASSWORD` — tu contraseña del SAC.
- `SAC_DOWNLOAD_DIR` *(opcional)* — directorio donde se guardan los adjuntos descargados por `download_adjunto`. Si no se setea, se usa el primer `root` que exponga el cliente MCP (Cowork, Claude Code), o `~/Downloads/bogamatic-sac/` como fallback.
### Actualizaciones automáticas
El flag `--refresh` en `args` hace que `uvx` re-resuelva contra PyPI en cada arranque de Claude Desktop. Así siempre tenés la última versión sin tocar el config. Trade-off: ~1-2 segundos extra al abrir Claude Desktop.
Si preferís pinear una versión específica (más rápido, sin auto-update), reemplazá:
```json
"args": ["--refresh", "bogamatic-sac-mcp"]
```
por:
```json
"args": ["bogamatic-sac-mcp==<version>"]
```
(por ejemplo `"bogamatic-sac-mcp==0.4.1"`). Después tenés que actualizar manualmente cada release.
Restart Claude Desktop.
## Available tools
- `get_novedades_cedulas` — list cedula notifications (NEW/SEEN)
- `get_detalle_cedula` — full cedula details
- `get_resumen_cedula` — cedula details + deadline calculation
- `get_expediente` — entry point for a chat: expediente metadata + `partes` block (actores, demandados, abogados grouped by side, with `esUsuario` and `ladoUsuario`).
- `get_expedientes` — search cases
- `get_novedades_expedientes` — recent case activity
- `get_operaciones_expediente` — case operations/movements
- `get_adjuntos_expediente` — case attachments
- `get_texto_operacion_expediente` — operation text (Markdown)
- `download_adjunto` — download an attachment. Destination cascade: MCP client root → `SAC_DOWNLOAD_DIR` env var → `~/Downloads/bogamatic-sac/`.
- `calcular_plazo` — calculate procedural deadlines
- `send_whatsapp_notification` — send WhatsApp alerts
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, but there is some overlap between get_detalle_cedula and get_resumen_cedula, with the latter explicitly combining the former with calcular_plazo. This could cause misselection, though descriptions help. Similarly, get_operaciones_expediente and get_texto_operacion_expediente are complementary but distinct.
All tool names follow a consistent snake_case verb_noun pattern, with 'get_' for retrieval, 'download_', 'calcular_', and 'send_' for actions. The singular/plural use (cedula/cedulas, expediente/expedientes) is logical and predictable. No mixed naming conventions are present.
With 12 tools, the server is well-scoped for its domain of legal case management and notifications. Each tool addresses a specific need, and the count is within the ideal range for a focused MCP server. No redundant or unnecessary tools are apparent.
The tool surface covers the primary workflows: listing and reading cedulas, searching and viewing expedientes, retrieving operations and attachments, downloading files, calculating deadlines, and sending notifications. Minor gaps exist, such as lacking a way to filter attachments by operation or explicitly marking a cedula as seen, but these are workable or handled automatically.