opentakeoff-mcp
Related Servers
Alternatives to opentakeoff-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceModern CAD CLI + MCP Server: 2D/3D drawing, editing, measurement, validation, batch automation, real-time collaboration (CRDT + WebSocket).221Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA local MCP server that drives PDFium and pypdf to perform comprehensive PDF operations including inspection, assembly, page editing, watermarking, rendering, extraction, form filling, encryption, compression, attachments, bookmarks, and metadata management.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for hard decoration quoting: parses DXF floor plans, reconstructs room topology, computes material quantities, and generates deterministic itemized quotes with tiered pricing. Exposes tools parse_dxf, compute_quote, and generate_report via stdio.-
- AlicenseAqualityBmaintenanceProvides construction-supervision tools for small-to-medium building projects, including stage guidance, inspection checklists, progress tracking, next-stage recommendations, and quotation analysis. It enables local, standards-based MCP interaction over stdio without third-party MCP SDKs.5MIT
- AlicenseAqualityAmaintenanceZero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.210MIT
- AlicenseBqualityBmaintenanceA local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.33MIT
TDQS
Scored across 53 tools
Most tools target clearly distinct resource+action verbs (measure_polygon vs measure_line vs measure_surface; create/list/resolve/delete_rfi). The main friction is a cluster of four counting tools (place_count, symbol_sweep, sweep_schedule_row, count_marks) and four exports (takeoff/report/marked_pdf/dxf), but the descriptions laboriously cross-reference each other to define boundaries. Boundaries are mostly legible, just heavy to read.
Almost uniformly snake_case verb_noun (load_plan, measure_polygon, edit_shape, create_rfi). The few noun-first names (sheet_info, sheet_graph, sheet_context) are a consistent convention for read/info tools, and there is no camelCase/snake_case mixing. Very predictable.
53 tools is well past the 25-tool threshold and into territory where the surface is hard to hold in mind at once. The domain (full takeoff workflow) is genuinely broad and justifies many tools, but several clusters (exports, counting sweeps, condition-edit proposals) could plausibly be consolidated. Heavy rather than well-scoped.
The surface covers the full lifecycle: load/read the plan set, measure and derive, edit and delete shapes, manage conditions/materials/proposals, four export formats, import round-trip, annotations, verdicts, RFI CRUD, and undo. Almost no dead ends; even deletion of annotations is handled via edit_annotation's clear-text path.