boq-mcp
Related Servers
Alternatives to boq-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides access to Autodesk Platform Services API, enabling interaction with ACC projects and issues through natural language.25MIT

co.geztio/platformofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and manage construction project economic data, including unit price analyses, resource catalogs, budget trees, and price lists, with secure multi-tenant access.MIT- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Autodesk Construction Cloud projects through natural language, connecting APS APIs for querying project data and issues.-
- AlicenseAqualityBmaintenanceEnables AI assistants to perform QC Database tasks such as uploading records, managing project turnover packages, and signing off on inspections via natural language.41MIT
- FlicenseNot gradedqualityBmaintenanceEnables natural-language querying of construction project data to analyze schedules, delays, critical activities, risks, and resource bottlenecks, and to generate schedule recovery recommendations.-
- FlicenseNot gradedqualityDmaintenanceConnects AI assistants to JoeAPI construction management system, enabling management of clients, contacts, proposals, estimates, action items, project schedules, and financial data through natural language.1-
TDQS
Scored across 19 tools
Each tool maps to a distinct resource/action: auth, hierarchical reads, creation, pricing costs, and contract/bill creation are clearly separated. The list_* and get_* read tools are distinguishable by level/aggregation, and create_* tools differ by target entity. No two tools appear to do the same job.
Almost all tools follow snake_case verb_noun conventions: list_projects, create_chapter, bulk_create_items, add_material_cost. Minor inconsistencies are login/whoami as standalone verbs and the mix of list_* for collections versus get_* for aggregate/singular reads, but the overall pattern is predictable.
19 tools is in the 16-25 range that feels heavy, though the BOQ domain spans hierarchy, pricing, and contracts so each tool has a distinct role. It is not egregiously over-scoped but exceeds the ideal 3-15 range for tight coherence.
The hierarchy has create/read coverage, but chapters/sections/items lack update/delete, and contractors/contracts/bills are write-only with no list/get tools. Pricing breakdown mentions labor/equipment/subcontracting, yet only material costs can be added. These gaps create dead ends for agents trying to verify or maintain created data.