Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@trane-mcp list all buildings and their current alarm status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
markdown
MCP server for Trane Technologies Tracer SC+ Building Automation System (BAS) API.
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.
Related MCP server: @inscada/mcp-server
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
Get full metadata for a single equipment unit including current health flags, model, and linked points.
Inputs: equipment_id (required).
List active alarms across the operator's Tracer SC+ deployment. Used by an on-call agent triaging what is unhealthy.
Inputs: status, limit.
List buildings managed by the operator's Trane Tracer SC+ instance. Standard read path for an agent that needs to enumerate the BAS surface.
Inputs: no named parameters.
List HVAC equipment at a building (AHUs, chillers, boilers, VAV boxes, fan coils, etc.). Used by an agent scoping work for a building.
Inputs: building_id (required).
Inventory operating schedules for buildings + equipment. Used by an agent planning around occupancy or seasonal modes.
Inputs: limit.
Inventory trend logs (historic telemetry). Used by an agent inspecting recent equipment behavior.
Inputs: equipment_id, limit.
Read the current value of a BACnet point on equipment (e.g. supply-air temperature, zone setpoint, damper position). Standard read path for live BAS state.
Inputs: equipment_id (required), point_name (required).
Write a new setpoint value to equipment. Gated by TRANE_ALLOW_SETPOINT_WRITE=true because writes change real HVAC behavior in real buildings. The MCP refuses unless the operator has explicitly authorized writes.
Inputs: equipment_id (required), point_name (required), value (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 8 tools
Each tool targets a distinct resource or action: equipment metadata, alarms, buildings, equipment list, schedules, trends, point read, setpoint write. No overlapping purposes.
All tools follow a consistent verb_noun pattern in snake_case (get_, list_, read_, set_). No mixing of conventions.
8 tools are well-scoped for a HVAC building management server, covering inventory, alarms, live data, and control without being excessive.
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.
Connect QuickBooks Online to AI agents with secure read or write access across multiple companies.
Read-only AI access to HAVN properties, leads, tasks, files, media, and analytics.
OT/ICS threat intel for AI agents: 40 tools, pay per call in USDC on Base via x402.
Provide AI agents and automation tools with contextual access to blockchain data including balance…
