opentakeoff-mcp
Related Servers
Alternatives to opentakeoff-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceModern CAD CLI + MCP Server: 2D/3D drawing, editing, measurement, validation, batch automation, real-time collaboration (CRDT + WebSocket).2220 PyPI2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA 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 gradedqualityBmaintenanceRuns 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.33 npm-
- AlicenseCqualityBmaintenanceEnables MCP clients to interact with OpenCode 2.x/3.x servers through direct /api/... HTTP routing and ~85 tools spanning sessions, messages, files, config, providers, projects, input, TUI, and workflows. Runs as a zero-dependency, pure-JavaScript stdio bridge with no SDK or build step.85MIT
- AlicenseNot gradedqualityBmaintenanceA local stdio MCP server that reads a PDF page from a local path or authorized download URL and renders it in memory, returning a real PNG image block plus page metadata. This lets an agent's vision model actually see handwriting, formulas, arrows, colors, and figures instead of only extracted text, with configurable DPI and clipping while reporting page count and size.1MIT
- 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.-
TDQS
Scored across 58 tools
The tool set is large but each tool has a largely distinct purpose: measurement verbs, counting verbs, export verbs, annotation/RFI verbs, and condition-editing verbs occupy separate niches. A few clusters require careful reading to distinguish (view_sheet vs sheet_context vs get_sheet_vectors; symbol_sweep vs sweep_schedule_row vs count_marks; export_report vs export_takeoff vs takeoff_summary), but the descriptions actively disambiguate them.
Almost all names are snake_case and action-oriented, with a predictable verb_noun or noun_noun pattern (measure_polygon, delete_shape, export_report, create_rfi, list_rfis). Minor deviations exist—some resource-first names like sheet_context, takeoff_summary, and estimate_summary, plus a few single-word verbs like annotate and cut_out—but overall the convention is readable and stable.
At 58 tools, the surface is very large and well beyond the typical 3–15 range, even for a full takeoff application. The domain is broad enough to justify many tools, but the count remains heavy and raises the risk of tool-selection overhead and overlap.
The surface covers an unusually full lifecycle: plan loading, scale calibration, measurement, counting/sweeping, conditions, materials, pricing, estimates, proposals, exports, annotations, verdicts, RFIs, schedule resolution, merge/duplicate handling, and undo. Minor gaps remain, such as no obvious standalone list-conditions or delete-condition verb, but most workflows have a supported path.