hcl-mcp
Related Servers
Alternatives to hcl-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables natural-language interaction with Ladybug Tools for building performance simulation, 3D modeling, and data visualization, allowing agents to perform complex environmental analysis tasks without CAD software.310GPL 3.0
- FlicenseNot gradedqualityAmaintenanceEnables natural language interaction with OpenStudio building energy simulation, allowing creation, querying, and modification of models, running EnergyPlus simulations, and analyzing results.44-

idfkit-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to create, edit, and simulate EnergyPlus building energy models via natural language. Supports schema exploration, model editing, simulation execution, and documentation search.393MIT- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with OpenStudio building energy models through natural language, allowing users to load, inspect, and manipulate OSM files including building geometry, HVAC systems, materials, schedules, and internal loads.11MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to understand, query, and manipulate Honeybee building energy models through natural language via the Model Context Protocol.17GPL 3.0
- AlicenseNot gradedqualityFmaintenanceWeather files (EPW/DDY) for building energy simulation, on-demand. Four tools: search the 17,000-station catalog, analyze any EPW (design conditions, HDD/CDD, DesignDay IDF emit), render 5 chart types (diurnal, wind rose, temp carpet, monthly box plot, comparison), and generate TMY/AMY/CMIP6-morphed scenarios with UHI, extreme events, and wildfire smoke overlays. 3 of 4 tools work without API key.MIT
TDQS
Scored across 51 tools
There are at least four exact duplicate pairs (validate/run_validation, presets/list_presets, reference/get_reference, weather/import_weather), and many simulation/sensor tools overlap heavily (run_annual vs annual_daylight vs lm83_daylight vs annual_nvrd; run_grid vs daylight_factor). An agent cannot reliably distinguish which tool to call.
Most names are readable snake_case, but the set mixes verb_noun (run_grid, import_geometry), noun_verb (glass_transmissivity, workplane_grid), and bare-noun tools (sensors, presets, reference, weather). The duplicate pairs use different conventions for the same function, so no predictable pattern emerges.
51 tools is far beyond the calibration threshold for a well-scoped server, and many are near-duplicates or aliases that inflate the surface without adding capability. This is an extreme mismatch between the number of tools and what a coherent HCL server needs.
The domain surface is genuinely broad: geometry import/health/sensors, sky/weather spectral reconstruction, annual/daylight/glare/circadian simulations, compliance, controls, and reporting are all present. Minor gaps exist (e.g. non-conformant LM-83 method, unsupported UL 24480, no Radiance install path), but agents can work around them.