processo-mcp
Related Servers
Alternatives to processo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceLocal-first MCP server that transforms civil case PDFs into queryable cases with structural provenance, evidence IDs, and page-level verification for drafting and factual review.22Apache 2.0
- AlicenseBqualityDmaintenanceA local, offline-first MCP server for searching, grepping, reading, rendering, and comparing long datasheet/TRM PDFs, using hybrid retrieval with BM25, dense embeddings, and visual page indexing.61MIT
- AlicenseAqualityCmaintenanceMCP server that enables local hybrid semantic and keyword search over private PDF, DOCX, Markdown, and text documents without sending data to embedding APIs.92,426 npmMIT
- AlicenseAqualityDmaintenanceA local-first MCP server that ingests PDFs, extracts structure, and provides semantic search and sequential navigation tools for AI clients to query and learn from documents.10MIT
- FlicenseAqualityDmaintenanceMCP server that enables semantic search over local PDF collections using local RAG, with automatic indexing of new documents.5-
- AlicenseAqualityDmaintenanceFast, local PDF parsing as an MCP server with text extraction, bounding boxes, OCR, and visual citations. No cloud or API key required.5MIT
TDQS
Scored across 12 tools
Most tools target distinct actions: preparation/extraction (preparar_caso), indexing (indexar_caso), search (buscar), verification (obter_pagina, validar_citacoes), and report generation (quadro_controversias). Only indice_pecas vs cronologia overlap somewhat, since both describe the process's pieces (index vs date-ordered timeline), but the descriptions distinguish them adequately.
All names use consistent lowercase snake_case in Portuguese with a clear domain suffix (_caso). The only deviation is mixed structure: some are verb-led (listar_casos, preparar_caso, validar_citacoes) while others are noun phrases (status_caso, cronologia, quadro_controversias), but the style remains predictable and readable.
Twelve tools map cleanly onto a coherent legal-case workflow: list → prepare (OCR) → index → search → verify → report. Each tool earns its place with no obvious redundancy or filler.
The surface covers the full research lifecycle, from PDF extraction and indexing through search, page verification, citation validation, and .docx report generation. Minor gaps exist (no explicit case creation/deletion or editing of the summary/status artifacts beyond resumo_caso), but these are workable.