thermal_load — engineering MCP Tool
thermal_load
(thermal load) is one of 27 tools on the
engineering
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call thermal_load from your client
- Claude Code engineering thermal_load run in your project directory
- Claude Desktop engineering thermal_load ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor engineering thermal_load ~/.cursor/mcp.json
- VS Code engineering thermal_load .vscode/mcp.json
- Zed engineering thermal_load ~/.config/zed/settings.json
- Windsurf engineering thermal_load ~/.codeium/windsurf/mcp_config.json
- Cline engineering thermal_load ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI engineering thermal_load ~/.gemini/settings.json
- Grok engineering thermal_load .mcp.json (in your project root)
- ChatGPT engineering thermal_load Settings → Connectors → Advanced → Developer mode
- Claude.ai engineering thermal_load Settings → Connectors → Add custom connector
- LangChain engineering thermal_load pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http engineering https://api.novtriq.tech/mcpOther tools on this server
- calculate_pue
- check_nis2_readiness
- assess_epbd_score
- estimate_cooling_load
- check_uae_bim_compliance
- check_uae_cybersecurity
- check_grid_feasibility_uae
- get_technical_dd_quote
- calculate_carbon
- roi_calculator
- building_carbon_footprint
- building_readiness
- eurocode_beam_designer
- eurocode_column_checker
- eu_cost_benchmarking
- dgnb_bim_readiness
- contractor_vetting
- digital_renovation_passport
- uk_planning_checker
- part_s_ev
- part_o_overheating
- mees_checker
- heatpump_heatloss
- eed_datacentre_pack
- uae_climate_ghg
- sap_sbem_precheck
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.