Vertiv Environet MCP. Get real-time data center environmental telemetry on demand.

This server plugs your AI client directly into critical data center environmental systems. It gives your agent real-time visibility across temperature, humidity, water leaks, smoke alarms, and more for every facility you run.

To start, if you don't know where the hardware is, you can use get_sites to pull a list of every facility ID tracked by Environet. Once you have those site IDs, you can use get_sensors to list all available environmental sensors deployed across those locations, figuring out exactly what points are being monitored.

Before running any checks, your agent should always run get_system_health. This confirms that the whole monitoring platform itself is actually online and reliable—you don't want to trust sensor data if the source feed is down. You can also check predefined safety parameters by calling get_thresholds, which reads the current high/low limits set for a specific sensor.

When you need immediate numbers, your agent uses get_sensor_reading to pull the single, live numerical reading from a specific point—say, the temperature in Rack A4 or the humidity in the UPS room. You can pair this with checking the current safety boundaries by calling get_thresholds so you know if that number is hitting compliance limits.

For active problems, your agent uses get_active_alerts. This function pulls a filtered list of all currently triggering alarms and warnings, letting you sort responses based on severity—Critical, Major, or Minor. When an alarm hits, you can mark it as handled by running acknowledge_alert. This action doesn't fix the problem, but it removes the alert from the live list and automatically updates the audit trail to log who investigated and when.

If you gotta dig into why something failed weeks ago, your agent runs get_alert_history, which pulls historical records for any specific alarm ID or site. This is what you use for root cause analysis or if someone asks you about SLA compliance. You can also run get_user_activity to get an audit log of every user action and configuration change within the Environet system, essential for security review.

If operational requirements change, your agent doesn't have to wait until a physical technician gets there; it uses update_threshold to immediately adjust the safety limits (high/low) for any given sensor, which changes what triggers future alarms right away. The server allows you to manage every aspect of monitoring—from listing sites with get_sites, finding all points with get_sensors, getting live readings via get_sensor_reading, and handling everything from initial alert triage using get_active_alerts to making sure the system is working correctly with get_system_health.

You can also audit who's doing what using get_user_activity while maintaining a strict record of all incidents through acknowledge_alert and comprehensive historical data via get_alert_history.