How to Use the Vertiv Environet MCP in Claude

Q: How do I use Vertiv Environet and Claude Desktop to get a site list?

First, run getsites. This gives you the master list of all monitored facilities. You then take those IDs to filter your sensor checks or alert queries.

Q: Can I check system health using Vertiv Environet and Claude Desktop?

Yep. Just run getsystemhealth. This verifies the monitoring platform itself is online and working right before you trust any of the sensor data coming back.

Q: How do I audit user actions in Vertiv Environet and Claude Desktop?

Run getuseractivity to pull an audit log of who did what. This is key for compliance checks. The resulting records show every user action within the Environet system.

Q: If I need to adjust alarm limits using Vertiv Environet and Claude Desktop?

You modify the limits with updatethreshold. This tool lets you change the trigger boundaries for a sensor. You'll likely check current limits first using getthresholds.

Check data center health and audit logs directly inside the Claude Desktop app.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Vertiv Environet MCP to Claude Desktop

Create your Vinkius account to connect Vertiv Environet to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Vertiv Environet with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Prioritize active alarms

Need to know what's smoking right now? Use `get_active_alerts` to pull all current environmental warnings. You can filter those alerts by site or severity, making sure you focus on the Critical items first. Don't just look at the list; use `acknowledge_alert` with both the `alertId` and your `userId`. This moves it off the active list and logs it correctly for handovers.

Diagnose root cause history

When something fails, you need to know why. Call `get_alert_history` if you want to track past alarms or identify recurring issues at a specific site. It's perfect for SLA reporting. If the problem is sensor-specific, run `get_sensors` first to list available points across sites, then use that data when checking historical records.

Monitor real-time equipment status

You need precise readings on critical gear. The tool `get_sensor_reading` gives you the current temperature or humidity from a specific asset. It's instant, actionable data. Want to check the limits? Use `get_thresholds` if you know the sensor ID. Otherwise, `get_sites` first helps you map out which facility that sensor belongs to.

Setup guide

Set up Vertiv Environet MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Vertiv Environet MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Vertiv Environet MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under vertiv-environet-mcp.

json

{
  "mcpServers": {
    "vertiv-environet-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Vertiv Environet Alert. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Vertiv Environet now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Vertiv Environet MCP in Claude Desktop

First, run `get_sites`. This gives you the master list of all monitored facilities. You then take those IDs to filter your sensor checks or alert queries.

Yep. Just run `get_system_health`. This verifies the monitoring platform itself is online and working right before you trust any of the sensor data coming back.

Run `get_user_activity` to pull an audit log of who did what. This is key for compliance checks. The resulting records show every user action within the Environet system.

This MCP Server deals with site IDs, sensor readings (temperature/humidity), alert IDs, user IDs, and configuration thresholds. It's a lot of operational metadata.

You modify the limits with `update_threshold`. This tool lets you change the trigger boundaries for a sensor. You'll likely check current limits first using `get_thresholds`.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript