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 gradedqualityCmaintenanceRuns 15 construction takeoff calculators — concrete, rebar, gravel, fill dirt, sand, topsoil, asphalt, lumber, roofing, fence, duct and paver base — directly from an MCP client, alongside a tool that lists them and a searchable table of source-cited estimating constants. Each call is computed by the bundled TakeoffMetric engine and returns structured quantities, order amounts, costs, warnings and assumptions.-
- 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
- AlicenseNot gradedqualityBmaintenanceLocal MCP server for PDF and photo tasks: merge, split, rotate and number PDFs, convert images to PDF, and inspect or strip hidden photo metadata (EXIF/GPS). Runs entirely on your machine — no uploads, no accounts, no API keys.MIT
TDQS
Scored across 53 tools
Most tools target a clearly distinct resource or action, and the descriptions explicitly cross-reference differences (e.g., measure_polygon vs measure_surface vs measure_line). However, several families overlap in purpose—sheet_info, sheet_context, sheet_graph, get_sheet_vectors, read_sheet_text, find_text, and view_sheet—and counting tools such as count_marks, symbol_sweep, and sweep_schedule_row sit close together. An agent can tell them apart only by reading the long descriptions carefully.
The entire set uses snake_case consistently, with no camelCase mixing, and many names follow verb_noun (measure_polygon, edit_shape, export_report, create_rfi). Minor deviations appear in noun-first names like takeoff_summary, sheet_info, sheet_graph, sheet_context, and export_marked_pdf. The pattern is predictable overall, just not uniformly verb_noun.
At 53 tools, this server far exceeds the typical 3–15 well-scoped range and crosses the rubric's 50+ extreme-mismatch threshold. Even though the domain is complex and many tools are specialized, the surface is too large for an agent to navigate reliably without heavy guidance.
The tool set covers a broad takeoff lifecycle: loading/importing/exporting plans and payloads, sheet inspection, measurement, derivations, counting, annotations, RFIs, condition and materials configuration, proposals, scope checks, undo, and approval marks. Minor gaps remain—no explicit delete_annotation or delete/list condition verb—though other tools and exports provide partial workarounds.