# MyLeadTech HVAC [Health: Active]

**Category:** 🏭 Industrial & IoT  
**Repository:** https://github.com/MyLeadTech/myleadtech-mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/myleadtech-hvac

## Description
HVAC MCP server — fault codes, model lookup and answers cited to the OEM manual page.

## Tools
Capabilities this server exposes over MCP:

- **resolve_equipment** — Turns a model or nameplate reference into brand and equipment, and reports coverage. Not charged.
- **search_hvac_documents** — Finds passages and citations in manufacturer documents.
- **get_hvac_source** — Returns a cited passage with bounded context.
- **answer_hvac_question** — A written answer with numbered, page-level sources.
- **get_hvac_document_page** — A source page as PNG, or a signed single-page PDF link when `format` is `pdf`.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "myleadtech-hvac": {
    "url": "https://mcp.myleadtech.app/mcp/"
  }
}
```

## Documentation

## What MyLeadTech HVAC MCP server does

The MyLeadTech HVAC MCP server gives an MCP-compatible client access to selected manufacturer documentation for Carrier, Trane, and Lennox equipment. Its main use is retrieving documentation-backed information about HVAC models, fault codes, specifications, and related service questions. Responses can include source identifiers, document details, passage text, and page references.

The service is hosted rather than implemented in this repository. The repository contains connection information and registry metadata for the remote endpoint at `https://mcp.myleadtech.app/mcp/`. Manufacturer coverage is limited to the brands listed above, so equipment from other brands is not documented as supported here.

## How it works

The MyLeadTech HVAC MCP server uses Streamable HTTP. An MCP client sends requests to the hosted endpoint and authenticates with `Authorization: Bearer <api_key>`. API keys are created through the MyLeadTech dashboard.

A typical workflow starts with `resolve_equipment`, which accepts a model or nameplate reference and reports the identified brand, equipment, and coverage. The result can guide later document searches or question answering. Searches and answers can receive a brand, model reference, fault code, language, and result limit. `operation_id` supports safe retries by replaying the earlier result instead of charging twice.

The service provides a sandbox allowance of 100 free units per month. Equipment lookups and clarifying questions do not count toward usage. The equipment-resolution operation is also described as not charged.

## Setup and configuration

Create an API key in the MyLeadTech dashboard before configuring a client. For Claude Code, add the remote server with the HTTP transport and an authorization header. Cursor uses a `.cursor/mcp.json` entry with the endpoint URL and header, while VS Code uses an HTTP server entry in `.vscode/mcp.json`.

Other clients can connect if they support remote Streamable HTTP MCP servers. Use the endpoint `https://mcp.myleadtech.app/mcp/` and provide the bearer token in the authorization header.

## Tools and capabilities

The MyLeadTech HVAC MCP server exposes five tools:

- `resolve_equipment` maps a model or nameplate reference to a brand and equipment record and reports coverage. It accepts `reference`, `market`, and `language`.
- `search_hvac_documents` finds relevant passages and citations in manufacturer documents. It supports questions, brand and model filters, fault codes, language, result limits, and an operation identifier.
- `get_hvac_source` retrieves a cited passage with bounded surrounding context using a `source_id`.
- `answer_hvac_question` produces a written response with numbered, page-level sources. It accepts the same main question and equipment filters as document search.
- `get_hvac_document_page` returns a source page as a PNG or provides a signed link to a single-page PDF. It requires a document version, page number, and format; an optional region can narrow the requested page area.

## Limitations and notes

The repository license is MIT for the README and configuration files only. That license does not cover the hosted MyLeadTech service or the manufacturer documents it cites. The available brand list is Carrier, Trane, and Lennox, and the service depends on a client that supports remote Streamable HTTP.

The example response in the README is a contract example rather than a live request. Generated answers and searches may incur usage, while retries using the same `operation_id` are not charged twice. A valid API key or supported account authentication is required for normal access.

_Full upstream README: https://allmcps.com/mcp/myleadtech-hvac/readme_