About hvac-quotes
HVAC equipment RFQ management: submit quotes to distributors
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx hvac-quotes-mcpHVAC_MOCK_EMAILSet to 'false' to send real emails via SMTP (default: 'true' for testing)SMTP_HOSTSMTP server hostname (for real email mode)SMTP_PORTSMTP server port (default: 587)SMTP_USERSMTP usernameSMTP_PASSSMTP passwordSMTP_FROMFrom email address for RFQsLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| quantity | integer | No | Number of units needed |
| equipment_type | enum | Yes | Type of HVAC equipment neededac_unit | furnace | heat_pump | air_handler | condenser | evaporator_coil | mini_split | thermostat | ductwork | other |
| needed_by_date | string | No | When equipment is needed (YYYY-MM-DD) |
| specifications | object | No | Equipment specifications |
| specifications.btu | integer | No | Heating capacity in BTU |
| specifications.seer | integer | No | SEER efficiency rating (e.g., 14, 16, 18, 20) |
| specifications.tonnage | number | No | AC/heat pump size in tons (e.g., 2, 3, 4, 5) |
| specifications.voltage | string | No | Required voltage (e.g., '208-230V', '460V') |
| specifications.refrigerant | string | No | Refrigerant type (e.g., 'R-410A', 'R-32') |
| specifications.additional_notes | string | No | Any additional requirements or notes |
| brand_preference | string | No | Preferred brand (e.g., 'Carrier', 'Trane', 'Lennox') |
| delivery_address | string | Yes | Full delivery address including city and state |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.