PJe-Calc MCP
Related Servers
Alternatives to PJe-Calc MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to connect to a running openLCA instance for life cycle assessment workflows, including building models, running calculations, auditing, and extracting data quality assessments.83 PyPI6-
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other AI agents to build, edit, and analyze Microsoft Project desktop schedules on Windows through natural language, covering tasks, WBS, dependencies, resources, calendars, baselines, critical path, resource leveling, and earned value, with live changes in Project and single-step undo. It also exports results to PDF or CSV and reads project health and time-phased data for S-curves and histograms.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control Windows CAD applications such as AutoCAD, ZWCAD, GstarCAD, and BricsCAD for drawing, layer and block management, entity manipulation, file operations, and data export through natural-language or direct commands.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants like Claude for Desktop or Cursor to drive Windows CAD applications (AutoCAD, ZWCAD, GstarCAD, and BricsCAD) via COM, executing 56 drawing, layer, block, entity, file, and export commands through natural-language or direct tool calls. Supports batch operations, multi-drawing session management, and data extraction to JSON or Excel.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control, automate, and query desktop project-management schedules in real time via native Windows COM, including task/WBS management, resource and cost assignment, baselines, critical path, status reporting, and PDF export.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants on Windows to inspect, edit, and save CorelDRAW documents through COM, including template-driven batch generation from CSV/Excel data and post-save verification.-
TDQS
Scored across 72 tools
Long descriptions carefully differentiate most tools, but real overlap remains: rest_tabelas_ultima_versao / rest_tabelas_versao / rest_tabelas_sincronizar_nacionais / rest_tabelas_sincronizar_regionais all look like table-sync tools yet are server-side endpoints that explicitly do NOT update tables, and calculo_validar vs calculo_pendencias vs calculo_criar vs calculo_gerar_pjc vs calculo_importar_pjc form a dense cluster. An agent must read whole descriptions to pick correctly, which is a sign of marginal boundary clarity at 72 tools.
Consistent snake_case with clear domain prefixes (calculo_, catalogo_, documento_, db_, rest_, config_, tabelas_, pjecalc_), which gives a predictable grouping. Minor deviations in verb/noun ordering (titulo_compor, processo_mapa, holerites_para_historicos, trct_para_pagamentos) but nothing chaotic.
72 tools is very heavy for a single desktop-app MCP; while the domain (labor calculation authoring, auditing, DB, config, REST) is genuinely broad, many REST/tabela/catalog tools could be consolidated into generic operations. The surface is well past the point where an agent can hold the catalog in mind.
Coverage is unusually thorough: document ingestion, interpretation planning, validation, PJC generation/import, liquidation, updates, reports, comparison, batch creation, DB backup/restore/query, config editing, app lifecycle, and REST service parity. No obvious dead ends in the stated workflow.