Kolmo Construction
Related Servers
Alternatives to Kolmo Construction
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRead-only MCP server for the Renology 2026 city-level renovation cost dataset. Enables AI assistants to list markets and project types, retrieve cost ranges, compare costs across cities, and access methodology and citation information.5MIT
- AlicenseAqualityBmaintenanceMCP server for the Housecall Pro API, letting AI assistants read and write Housecall Pro data—customers, jobs, invoices, estimates, scheduling, and more—through natural language.4117 npmMIT
- 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
- FlicenseNot gradedqualityBmaintenanceMCP server for HERO handyman software, providing 34 OAuth-secured read/write tools with multi-tenant support and built-in API correctness checks.-
- AlicenseNot gradedqualityBmaintenanceEnables managing home renovation projects through natural language, covering floors, spaces, budgets, renovation items, schedules, dependencies, notes, and vendor activity via a remote MCP endpoint.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for MACD Adaptive (macd.ie), a Dublin web design studio: services, pricing, availability, quote estimates and discovery calls. Remote (https://macd.ie/mcp), stateless, no auth, English/Spanish.-
TDQS
Scored across 36 tools
Most tools have distinct resources and actions, but several clusters overlap: check_permit_requirements, get_permit_rule_details, answer_permit_question, and resolve_permit_submittals all cover permit questions; get_material_options and get_material_catalog both serve material discovery; get_project_testimonials and list_reviews overlap; and get_neighbor_permit_activity vs get_neighborhood_project_activity are very similar in name and scope. The detailed descriptions help disambiguate, but misselection is still a real risk.
Tool names follow a highly consistent snake_case verb_noun pattern throughout: list_*, get_*, check_*, estimate_*, resolve_*, lookup_*, parse_*, answer_*, and submit_*. Even longer names like check_service_area_coverage and get_permit_data_freshness preserve the same convention with no mixed casing or arbitrary verb styles.
36 tools is well above the 25+ threshold and feels heavy even for a broad construction company MCP. The count is padded by overlapping permit tools and multiple discovery/list endpoints that could likely be consolidated without losing capability.
The tool surface covers the main homeowner and contractor journeys remarkably well: estimating, materials, permits, services, projects, reviews, blog content, financing, ROI, weather, and service-area checks. Minor gaps exist—such as no dedicated commercial-service detail endpoint and no scheduling/booking tool—but submit_contact_request and the rich listing tools allow agents to work around them.