What types of sensors are supported?

Environet supports temperature, humidity, differential pressure, airflow, water leak detection, and smoke sensors. These are typically deployed in server racks, raised floors, and UPS rooms.

Can I adjust alarm thresholds via the API?

Yes! Use the update_threshold action to modify high and low limits for specific sensors. This is useful for seasonal adjustments or when deploying new equipment with different thermal requirements.

Is the API accessible remotely?

Typically, the Environet API is hosted on the local infrastructure (on-premise server) where the Environet software is installed. You will need the internal IP or hostname and the API Key provided by your Vertiv admin.

Vertiv Environet MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Vertiv Environet
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Vertiv Environet through Vinkius, pass the Edge URL in the `mcps` parameter and every Vertiv Environet tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Vertiv Environet Specialist",
    goal="Help users interact with Vertiv Environet effectively",
    backstory=(
        "You are an expert at leveraging Vertiv Environet tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Vertiv Environet "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Vertiv Environet MCP Server

Connect Vertiv Environet Alert to any AI agent and gain real-time visibility into your critical infrastructure's environmental health — temperature, humidity, water leaks, smoke, and active alarms.

When paired with CrewAI, Vertiv Environet becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Vertiv Environet tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Site Management — List all monitored facilities and data centers
Sensor Monitoring — Retrieve real-time readings from temperature, humidity, and airflow sensors
Active Alerts — View and filter active alarms by severity (Critical, Major, Minor)
Alert Acknowledgement — Acknowledge alerts to track operator response and maintain audit trails
Threshold Management — View and update high/low limits for environmental sensors
Alert History — Analyze historical alarm data for root cause analysis and SLA reporting
System Health — Verify the monitoring platform's operational status
Audit Logs — Review user activity and configuration changes for compliance

The Vertiv Environet MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Vertiv Environet to CrewAI via MCP

Follow these steps to integrate the Vertiv Environet MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Vertiv Environet

Why Use CrewAI with the Vertiv Environet MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Vertiv Environet through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Vertiv Environet + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Vertiv Environet MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Vertiv Environet for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Vertiv Environet, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Vertiv Environet tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Vertiv Environet against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Vertiv Environet MCP Tools for CrewAI (10)

These 10 tools become available when you connect Vertiv Environet to CrewAI via MCP:

acknowledge_alert

Requires the alertId and the userId of the operator acknowledging it. Acknowledged alerts are removed from the "active" list and moved to history. Essential for audit trails and shift handovers. Acknowledge an active alarm to indicate it is being investigated

get_active_alerts

Can filter by severity (Critical, Major, Minor, Warning) or by site. Critical alerts often indicate immediate risk to equipment or operations. Use this to prioritize operational response. Get currently active environmental alarms and warnings

get_alert_history

Optional siteId and limit parameters. Use this for root cause analysis, SLA reporting, or identifying recurring environmental issues. View historical alarm records for analysis and reporting

get_sensor_reading

Use this for precise monitoring of critical assets (e.g., specific server rack temperature or UPS room humidity). Get the current real-time reading from a specific sensor

get_sensors

Optional siteId filters results to a specific facility. Use this to discover available monitoring points. List environmental sensors deployed across monitored sites

get_sites

Use this to identify which site IDs to use for further filtering of sensors and alerts. List all monitored sites and facilities in the Environet system

get_system_health

Use this to verify if the monitoring platform is online and functioning correctly before trusting sensor data. Check the operational status of the Environet monitoring system itself

get_thresholds

Optional sensorId filters to a specific sensor. Use this to audit current safety limits and ensure they match operational requirements. View configured alarm thresholds for sensors

get_user_activity

Use this for security auditing and operational compliance. View audit log of user actions within the Environet system

update_threshold

Changes trigger new alarms if readings cross the new boundaries. Use this to adjust sensitivity based on seasonal changes or equipment updates. Modify alarm thresholds for a sensor

Example Prompts for Vertiv Environet in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Vertiv Environet immediately.

"Show me all critical environmental alerts right now."

"What's the current temperature in Server Room B?"

"Acknowledge alert ID 98765 by operator Admin."

Troubleshooting Vertiv Environet MCP Server with CrewAI

Common issues when connecting Vertiv Environet to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Vertiv Environet + CrewAI FAQ

Common questions about integrating Vertiv Environet MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.