trane-mcp
by NoBanks
README.md
markdown
# trane-mcp
MCP server for Trane Technologies Tracer SC+ Building Automation System (BAS) API.
## Overview
This MCP server provides AI agents with read access to Trane Tracer SC+ building automation systems. It wraps the Tracer SC+ API Builder surface to enable inventory and telemetry retrieval for buildings, equipment, BACnet points, alarms, schedules, and trend logs.
Tracer SC+ is a self-hosted building automation controller from Trane Technologies. This server connects to a customer's deployment and exposes 8 tools for agent-based BAS operations.
## Features
- **Read-only by default** - All tools are read operations that do not modify HVAC behavior
- **8 BAS tools** - Buildings, equipment, points, alarms, schedules, and trends
- **Setpoint writes gated** - Requires explicit `TRANE_ALLOW_SETPOINT_WRITE=true` env var
- **Async httpx client** - Non-blocking API calls with 60s timeout
- **Pydantic v2 schemas** - Type-safe inputs and outputs
- **SSL verification toggle** - Supports self-signed dev certificates
## Installation
TDQS
A3.7/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct resource or action: equipment metadata, alarms, buildings, equipment list, schedules, trends, point read, setpoint write. No overlapping purposes.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (get_, list_, read_, set_). No mixing of conventions.
Tool Count5/5
8 tools are well-scoped for a HVAC building management server, covering inventory, alarms, live data, and control without being excessive.
Completeness4/5
Covers monitoring and basic control (setpoint write) but lacks operations like schedule modification or alarm acknowledgment, which are minor gaps for the typical use case.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues