ESXi MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is ESXi MCP Server?

ESXi MCP Server is a VMware ESXi/vCenter management server that utilizes the Model Control Protocol (MCP) to provide a simple REST API interface for managing virtual machines.

how to use ESXi MCP Server?

To use the ESXi MCP Server, install the required dependencies, create a configuration file with your vCenter details, and run the server using Python.

key features of ESXi MCP Server?

  • Supports connections to ESXi and vCenter Server.
  • Real-time communication using Server-Sent Events (SSE).
  • RESTful API interface with JSON-RPC support.
  • API key authentication for secure access.
  • Complete lifecycle management for virtual machines.
  • Real-time performance monitoring capabilities.
  • SSL/TLS secure connection support.
  • Flexible configuration options using YAML/JSON/Environment Variables.

use cases of ESXi MCP Server?

  1. Managing virtual machines in a VMware environment.
  2. Monitoring performance metrics of virtual machines.
  3. Automating VM lifecycle operations such as creation, deletion, and power management.

FAQ from ESXi MCP Server?

  • What are the requirements to run ESXi MCP Server?

You need Python 3.7+, along with specific libraries like pyVmomi and PyYAML.

  • Is there an authentication mechanism?

Yes, all privileged operations require API key authentication.

  • Can I monitor VM performance?

Yes, the server provides real-time performance monitoring for CPU, memory, storage, and network traffic.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago