Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
The New Engineer — HVAC is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
IFC models: duct networks, circuits, pressure drop. EN 12828 vessels, EN 378, Swiss refrigerants.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http the-new-engineer-hvac-mcp https://thenewengineer.com/mcp
# 2 — ask your agent for something these tools do
# size_expansion_vessel, water_content_from_vessel, check_refrigerant_switzerland and 8 more
The New Engineer — HVAC costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 1 server
thenewengineer1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http the-new-engineer-hvac-mcp https://thenewengineer.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the standard's tables and formulas, never from a language model's estimate. Every step is auditable. Size the expansion vessel and pressurisation of a closed heating or chilled-water circuit to EN 12828: static height, minimum pressure p0, fill pressure pa, final pressure pe, expansion
| Parameter | Type | Required | Notes |
|---|---|---|---|
| installation_volume_l | number | yes | Total water content of the closed circuit, in litres: pipes, emitters, generator, buffer tank. THIS IS THE WATER, NOT THE VESSEL. If you know the vessel and want the water content, this is the wrong t |
| highest_point_above_unit_m | no | Height of the REAL highest point of the installation - the top air vent - above the point where the expansion vessel connects to the network, in metres. Taken as given: no margin is added. NEEDED FOR | |
| lowest_point_from_unit_m | no | Height of the REAL lowest point of the installation - the lowest drain - relative to the point where the expansion vessel connects to the network, in metres. NEGATIVE when below it, 0 when the vessel | |
| safety_valve_from_unit_m | no | Height of the safety valve relative to the point where the expansion vessel connects to the network, in metres. The safety valve always sits on the heat generator (boiler, heat pump) or chiller - tell | |
| installation | no | 'chauffage' for heating, 'refroidissement' for cooling / chilled water. Omit: heating. | |
| fluid | no | Heat-transfer fluid: 'eau' (Water), 'meg' (MEG), 'mpg' (MPG), 'tyfocor' (TYFOCOR L (MPG)). Omit: plain water. | |
| glycol_pct | no | Glycol concentration in %, ignored for water. Defaults to 30 %. | |
| flow_temperature_c | no | Flow temperature, °C. Omit: 80 in heating, 6 in cooling. | |
| return_temperature_c | no | Return temperature, °C. Omit: 60 in heating, 12 in cooling. | |
| filling_temperature_c | no | Temperature at which the circuit is filled, °C. Omit: 10. | |
| min_temperature_c | no | LOWEST temperature the fluid can reach, °C — including a breakdown, not just normal running. Omit and the filling temperature is used; in a glycol mix the calculation already goes down to the frost pr | |
| design_temperature_c | no | Hottest the fluid ever gets, standstill included. Omit: the warmer of flow and return in heating, 40 °C in cooling. | |
| pressurisation | no | Type of pressurisation: 'statique' (Pressure-maintained by gas cushion (Statico)), 'compresseur' (Compressor-driven (Compresso)), 'pompe' (Pump-driven (Transfero)). Omit: gas-cushion vessel. | |
| safety_valve_setting_bar | no | Safety valve setting in bar, one of the standard settings. Omit to take the smallest standard setting that works here. A setting below the minimum the installation needs is raised, and the result says | |
| minimum_required_pressure_bar | no | Pressure the installation requires at the pressurisation unit whatever the height - against cavitation at a pump suction, for instance. p0 never falls below it. Omit: zero. | |
| language | string | no | The user's language, for labels and alerts. |
DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the standard's tables and formulas, never from a language model's estimate. Every step is auditable. Deduce the water content of an installation from the expansion vessel already fitted. WHAT THIS IS FOR. Refurbishment, and site visits with no drawings. Sizing a new vessel, a new pump or a new
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vessel_volume_l | number | yes | Nominal capacity of the expansion vessel actually installed, in litres — read it on the nameplate. |
| flow_temperature_c | no | Design flow temperature, °C. In heating this is the highest the water reaches. | |
| return_temperature_c | no | Design return temperature, °C. | |
| pressurisation | string | no | How pressure is held: 'static' for a plain membrane vessel, 'compressor' for a compressor unit (Compresso and the like), 'pump' for a pump unit. A compressor or pump unit holds the pressure itself, so |
| static_height_m | no | Height of the highest point above the vessel, in metres. Required for 'static' only — a compressor or pump unit does not use it. | |
| valve_setting_bar | no | Safety valve setting, bar. Required for 'static' only. | |
| fill_temperature_c | no | Temperature the water was at when the system was filled, °C. 10 °C is the usual mains temperature indoors. Ask, or state the assumption. | |
| min_temperature_c | no | LOWEST temperature the fluid can reach, °C — including a breakdown, not just normal running. Indoors, 10 °C. Outdoors, 0 °C, or down to the freezing point of the glycol mix. This is what fixes the ref | |
| max_temperature_c | no | HIGHEST temperature the fluid can reach, °C — in extreme conditions, running OR stopped. In heating it is the flow temperature. In cooling it is not the regime at all: a stopped chiller lets the water | |
| fluid | string | no | Heat-transfer fluid: 'eau' (Water), 'meg' (MEG), 'mpg' (MPG), 'tyfocor' (TYFOCOR L (MPG)). |
| glycol_percent | number | no | Glycol concentration in %, ignored for water. |
| installation | string | no | 'heating' or 'cooling'. |
DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the regulation's annexes and thresholds, never from a language model's estimate. Every step is auditable. Swiss refrigerant regulation check (ORRChim / ChemRRV annex 2.10, OFEV synthesis of May 2026, rules adopted 29.10.2025) plus refrigerant data from EN 378-1 Annex E: GWP (AR4, the ORRChim ba
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refrigerant | string | yes | Refrigerant designation as the user wrote it: 'R-32', 'R410A', 'R1234ze', 'CO2', 'propane'… |
| application | no | Use of the installation: 'climatisation_batiment' (building cooling, incl. reversible heat pump used mainly for cooling), 'froid_alimentaire_positif' (food/perishables, use temp ≥ 0 °C), 'froid_alimen | |
| cooling_capacity_kw | no | Peak useful cooling capacity Q0K, kW. Omit if unknown. | |
| heating_capacity_kw | no | Peak useful heating capacity Q0H, kW (heat pumps). Omit if unknown. | |
| refrigerant_charge_kg | no | Total refrigerant charge, kg. Omit if unknown. | |
| self_contained | no | True if 'autonome': factory-built circuits in a frame/casing and no gas-carrying part connected on site (packaged chiller, monobloc heat pump, rooftop). Omit if unknown. | |
| split | no | True for a split system (indoor/outdoor units linked by refrigerant lines laid on site). Omit if unknown. | |
| direct_expansion | no | True if the refrigerant evaporates directly in the room units / evaporators (DX, incl. VRF); False if it cools a water or brine loop. Omit if unknown. | |
| secondary_circuit | no | True if cold is distributed through a secondary coolant loop (chilled water, glycol, brine). Omit if unknown. | |
| air_cooled_condenser | no | True if heat is rejected through an air-cooled condenser (heat pump: its air heat exchanger). Omit if unknown. | |
| evaporator_count | no | Number of evaporators. | |
| refrigerant_circuit_count | no | Number of refrigerant circuits. | |
| heat_recovery | no | True if rejected heat is recovered. | |
| simultaneous_heating_cooling | no | True for simultaneous heating and cooling with at least 2 air heat exchangers. | |
| gwp_if_unlisted | no | ONLY if a previous call said the refrigerant is not in the database: its GWP (AR4) from the manufacturer's datasheet, given by the user. | |
| odp_if_unlisted | no | ONLY with gwp_if_unlisted: its ODP (0 for HFC/HFO). | |
| family_if_unlisted | no | ONLY with gwp_if_unlisted: 'naturel' (natural), 'stable' (contains any HFC/PFC — e.g. R-454B, R-454C, R-455A), 'hfo' (only HFO and/or natural components). | |
| language | string | no | The user's language, for labels. French or English text; translate for de/it/es. |
DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the standard's tables and formulas, never from a language model's estimate. Every step is auditable. EN 378 applied to BUILDING projects, volume by volume. An installation does not occupy one room but several: the machine, the rooms crossed by refrigerant lines, the rooms served by indoor unit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refrigerant | string | yes | Refrigerant as the user wrote it: 'R-32', 'R410A', 'R290', 'R717', 'propane'… |
| configuration | no | How the installation is laid out. Omit if unknown: the tool returns the question to ask. | |
| charge_kg | no | Refrigerant charge of the largest circuit, in kg. | |
| volume_local_m3 | no | Volume of the plant room, in m³. | |
| volume_enceinte_m3 | no | Volume of the ventilated enclosure, in m³. | |
| volume_local_desservi_m3 | no | Volume of the smallest room crossed or served by an indoor unit, in m³. | |
| surface_local_desservi_m2 | no | Floor area of that room, in m². Formula C.2 needs it; without it the tool returns the minimum area required instead. | |
| pose | no | How the indoor unit is mounted: on the floor, wall, window or ceiling. Formula C.2 depends on it. | |
| acces_local | no | Access category of the plant room. Omit: 'c', authorised persons only. | |
| acces_locaux_desservis | no | Access category of the rooms crossed or served: 'b' for offices, laboratories, workplaces; 'a' for hotels, schools, shops, hospitals, homes. | |
| language | string | no | The user's language. Texts are in French: translate them. |
CALL THIS FIRST, as soon as the user gives you a token. It answers within seconds, while the network graph is still being built - use that time to think. THE CIRCUITS OF A MODEL IN FOUR CALLS: 1. read_ifc_overview - this call: the types of the model. 2. apply_ifc_rules - your rules. Give air handling units, monoblocs and ventilation casings the role centrale_de_traitement_d_air, and
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The token from the link the user pasted — the last part of thenewengineer.com/ia/XXXX. Valid 48 hours. |
Turn what you read in the overview into rules the tool replays on EVERY piece of the model, including the ones you were never shown. THIS IS HOW THE TOOL LEARNS A MODEL. read_ifc_overview gives you some fifty groups — one per object type, not one per piece. You answer with RULES on those groups, and this tool applies them to the three thousand pieces. You never give a verdict piece by piece: the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The model token, from ifc_upload_result or from the link the user pasted. |
| rules | object | yes | Your rules, as a JSON object. The only required key is roles.liste: an ORDERED list, FIRST MATCH WINS, most specific first. Each entry is {"role": "a_name", "si_un_de": [conditions]} and may also carr |
DETERMINISTIC: networks come from geometry, not from a guess. The same model always gives the same networks, from any AI, on any day. Read the networks of an IFC model already uploaded by the user. WHAT A NETWORK IS. A set of parts that touch each other, cut at equipment: a pump, an air handling unit, a chiller separates two systems, so the tool does not run through them. This is measured on the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The token from the link the user pasted. It looks like the last part of thenewengineer.com/ia/XXXX. The user gets it on the model page, button 'share with my AI'. Valid 48 hours, one model. |
Apply the names you propose, and get back the updated report. THE NAMES ARE YOURS, THE NETWORKS ARE NOT. You are naming what the tool measured; you are not changing what it measured. Nothing you send here alters a network, a part, or a correction. WHAT COMES BACK. The updated report, a 3D link where the user sees your names in colour, and a link to the corrective Dynamo script that writes the sy
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The same token used with read_ifc_networks. |
| names | object | yes | One name per network, keyed by its 'rang' as a string, for instance: {'3': 'SUPPLY L2', '7': 'EXTRACT KITCHEN'}. Only include the ones you are naming; the others are left untouched. |
| reasoning | no | One short line per name, saying what it is based on — the neighbouring unit, the project's naming scheme, an existing system. Shown to the user, who decides. |
THE CIRCUITS THE FANS OF A MODEL ARE SIZED ON, AND THEIR PRESSURE DROP, without anyone clicking. FIRST THE LIST, THEN THE CALCULATION. Called with only the token, once your rules are posted with apply_ifc_rules, it computes NOTHING and bills nothing: it returns the COMPLETE list of the model's systems ('systemes', each with the units that serve it) and of its air handling units and fans ('central
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | The model token, from ifc_upload_result or from the link the user pasted. |
| start_guid | no | Leave EMPTY in general. The piece the AIR LEAVES FROM - an air handling unit, a fan, or the duct end where the air enters: circuits are computed from it. A GlobalId from 'equipements' in the answer of | |
| end_guid | no | The END of ONE circuit the user wants - a terminal, a louvre, any duct. With start_guid: the circuit from start to end. Alone: the tool finds the start of that network, as for network_guid. Only this | |
| network_guid | no | ANY piece of the network the user wants computed - a duct, a terminal, a fitting - when the model has no unit, when the user's unit was not recognised, or when they simply point at the network. The to | |
| start_role | no | Rarely needed. Computes every piece your rules gave this role - centrale_de_traitement_d_air or ventilateur -, like all_networks restricted to one role, and only on a model of 50 air networks or fewer | |
| max_velocity_m_s | no | Design velocity, in m/s, 0.5 to 12. It sets the flow rate at the start of each circuit when flow_m3h is not given, and the flow after each branch: between two branches, the length-weighted average vel | |
| flow_m3h | no | Flow rate leaving ONE starting part, m3/h - so give it with start_guid. Over the whole model it would give every unit the same flow, and the call refuses it when there are several: compute the model w | |
| unit_name | no | Only when the user asks about ONE unit or fan: its name, or a part of it - « CTA 12 », « AHU-Supply-L2 ». The tool looks it up among EVERY piece your rules gave the role centrale_de_traitement_d_air o | |
| systems | no | Systems to compute, by name - from 'systemes' of the list answer, or from read_ifc_networks. Each brings in the WHOLE air handling unit or fan that serves it (supply, return, outdoor air, exhaust); a | |
| units | no | Air handling units or fans to compute, by name - from 'centrales_et_ventilateurs' of the list answer, or from 'equipements' of apply_ifc_rules. Same matching as systems. Can be combined with systems. | |
| all_networks | no | True computes the WHOLE model: every unit and fan, and a supposed start for each network none of them serves. Offered only when the list answer says 'tous_possible': 50 air networks or fewer. Use it w | |
| excluded_guids | no | Parts to close, by GlobalId. Closing a part cuts the walk there: whatever was only reached through it leaves the survey. Use it when the network visibly runs too far - through a plenum shared with ano |
Show an upload box in the conversation where the user can drop an IFC file (.ifc) of a building services model (HVAC, plumbing, heating). The file goes straight from the user's browser to thenewengineer.com - you never see it. CALL THIS when the user wants to analyse an IFC model and has not yet given you a link from thenewengineer.com. Then tell the user to drop the file in the box. When the up
No parameter schema on file.
Where the upload stands. When state is depose, token is the token to pass to read_ifc_networks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| upload_token | string | yes | The upload_token returned by open_ifc_upload. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install The New Engineer — HVAC or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.0.
1.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish The New Engineer — HVAC can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.