Skip to main content
Glama
bogamatic-sac-mcp

bogamatic-sac-mcp

by inncode-io

bogamatic-sac-mcp

MCP server for interacting with the Argentine judiciary system (SAC - Justicia Cordoba) via Claude Desktop.

Installation

Requires Claude Desktop and uv.

Add to your claude_desktop_config.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á:

"args": ["--refresh", "bogamatic-sac-mcp"]

por:

"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.

Related MCP server: legal-ar-mcp-hub

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

Available Tools

12 tools
calcular_plazoA

Given a notification date (typically from a cedula), calculates the first day a procedural deadline begins to run. Cordoba's (Argentina) procedural law grants 3 grace days after notification before any deadline starts. This tool counts 3 business days forward (skipping weekends and court holidays) and returns the date when the deadline period actually begins.

Inputs: fecha (required).

download_adjuntoA

Download an attachment locally. Works for both cedulas (get_detalle_cedula adjuntos[]) and expediente operations (get_adjuntos_expediente). The destination is chosen by: (1) the first file:// root from the MCP client (e.g. Cowork project dir or Claude Code project dir), (2) the SAC_DOWNLOAD_DIR env var, or (3) ~/Downloads/bogamatic-sac/. The file is named {numeroExpediente}{fechaOperacion}{fileName}.

Inputs: idAdjunto (required), idOperacion (required), fechaOperacion (required), numeroExpediente (required). Returns: result

get_adjuntos_expedienteA

Get all attachments for an expediente. Each item returns: idFichero, idOperacion (prefixed E:/O: — pass through as-is to other tools), nombre (file name), fecha (dd/MM/yyyy), tipoOperacion, clasificacion, observaciones. Use idFichero, idOperacion and nombre as inputs for download_adjunto.

Inputs: idExpediente (required). Returns: result

get_detalle_cedulaA

Get the full detail of a specific cedula notification. Returns: matricula, destinatario, dependencia, numeroExpediente, caratula, fecha (dd/MM/yyyy), tipoOperacion, idOperacion, textoOperacion (converted to Markdown), protocolo, and adjuntos[] (each with idFichero, nombre, datosExtra).

Inputs: idCedula (required).

get_expedienteA

Look up a single expediente (case) by its numeroExpediente OR idExpediente. Use this at the start of any chat about a case — it returns the full expediente record plus a partes block grouping actores, demandados, and abogados (with abogadosActor / abogadosDemandado). The ladoUsuario field tells you which side of the litigation the authenticated lawyer is on ("actor", "demandado", or null if no match). The lawyer matching the user's matrícula has esUsuario: true. If the partes fetch fails, partes is null and partesError carries a short reason. Use the returned idExpediente to drive subsequent tools (get_operaciones_expediente, get_adjuntos_expediente).

Inputs: idExpediente, numeroExpediente.

get_expedientesA

Search legal expedientes (cases/files) belonging to the authenticated lawyer. Supports fuzzy search on 'caratula'. Partial names are valid. If the user provides an expediente number, prefer using 'numeroExpediente' as the primary filter because it uniquely identifies the expediente.

Inputs: caratula, pageSize, pageIndex, fechaDesde, +2 more. Returns: result

get_novedades_cedulasA

Get the list of electronic cedula notifications (novedades). Each cedula is marked as 'NEW' or 'SEEN'. New cedulas are those not previously fetched. All fetched cedulas are stored to avoid duplicate notifications.

Inputs: pageSize, pageIndex, sortColumn, sortDirection.

get_novedades_expedientesA

Get expedientes (cases) that had activity in the last 7 days. Returns case number, title, court, status, and location.

Inputs: pageSize, pageIndex. Returns: result

get_operaciones_expedienteA

Get all operations (movements) for a specific expediente. Each operation returns: fecha (dd/MM/yyyy), tipoOperacion, idOperacion (prefixed E:/O: — pass through as-is to other tools), adjunto (boolean), firmada, presentadoPor, ubicacion, estado, and a flattened extras dict.

Inputs: idExpediente (required), includeEspeciales. Returns: result

get_resumen_cedulaA

Get a complete summary of a cedula in a single call. Combines get_detalle_cedula + calcular_plazo into one response. Returns: destinatario, numeroExpediente, caratula, dependencia, fecha, tipoOperacion, idOperacion, textoOperacion (Markdown), adjuntos[] (each with idFichero, nombre, datosExtra), protocolo, and plazo (with fechaInicio, fechaPlazo, diasHabilesContados, diasSaltados). Use this instead of calling get_detalle_cedula and calcular_plazo separately.

Inputs: idCedula (required).

get_texto_operacion_expedienteA

Get the text content of an operation within an expediente as Markdown. Pass the idOperacion (with its E:/O: prefix) exactly as returned by get_operaciones_expediente or get_adjuntos_expediente.

Inputs: idOperacion (required). Returns: result

send_whatsapp_notificationA

Send a WhatsApp notification about a cedula. The recipient phone number is resolved automatically from the authenticated user's account. The cedula details (destinatario, fecha, tipoOperacion, numeroExpediente, caratula) are loaded server-side from idCedula — the same ID used by get_resumen_cedula.

Inputs: idCedula (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 12 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to Brazilian judicial data from DataJud CNJ and 91 courts, enabling process consultation, monitoring, and deadline calculation under the Civil Procedure Code.
      9
      178 PyPI
      141
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to query Brazil's DataJud (CNJ) public court API with typed, validated, retry-safe tools: fetch a case by its CNJ number with check-digit validation and automatic court resolution, list a case's movements with plain-English hints, search cases by class, subject, court unit or filing dates, and list all 91 court indices. Responses are returned as structured content, making court case metadata usable from Claude Desktop, Claude Code, or a custom agent.
      4
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables natural-language queries of Brazilian court cases through the public DataJud and DJEN APIs, retrieving case details, movements, publications, and parties across 92 tribunals, and calculating procedural deadlines in business days. It also offers optional Domicílio Judicial Eletrônico tools for listing and acknowledging intimations.
      11
      MIT