HVAC Builder

app.hvacbuilderPublished by hvacbuilder.appOfficial publisherv1.0.0Updated Oct 24, 2026

Design, solve and simulate HVAC systems from real components, weather years and buildings.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote MCP server that lets an assistant design, solve and simulate HVAC systems using real components, weather years and buildings.

What you can do
Design HVAC systems from real components and buildings, with the assistant working through the design task on the user's behalf. Solve HVAC systems, using real weather-year data as input. Simulate HVAC systems to see how a design behaves. The server exposes no tool list, so the exact operations available are not documented here.
When to use it
Useful when an assistant needs to work on HVAC design, sizing or performance questions and the user wants results grounded in real components, buildings and weather data rather than rough estimates.
Requirements
A remote streamable HTTP endpoint at hvacbuilder.app. Authentication is required via OAuth, so the user must sign in with an account on that service. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth account on a third-party service, so review what that account shares before connecting. The server's tools are not listed, so it is unclear whether designs are saved, changed or deleted, or what project data is sent to the provider. Confirm pricing and data handling on the provider's site first.

Installation

In SourceWeft

  1. Open HVAC Builder in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.hvacbuilder%2Fhvac-builder/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "hvac-builder": {
      "type": "http",
      "url": "https://hvacbuilder.app/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.