VME MCP Server

Created By
frippe75a year ago
Intelligent VMware MCP Server with Natural Language Processing for Infrastructure Management
Overview

what is VME MCP Server?

VME MCP Server is an intelligent Model Context Protocol (MCP) server that allows users to manage HPE VM Essentials (VME) infrastructure through natural language commands, simplifying the process of provisioning and managing virtual machines.

how to use VME MCP Server?

To use VME MCP Server, clone the repository, set up your environment with the necessary credentials, and add the server to Claude Code. You can then issue commands in plain English to manage your VMs.

key features of VME MCP Server?

  • Natural Language Processing for flexible command input
  • Intelligent distribution of VMs across cluster nodes
  • Automatic resource resolution for the latest OS versions

use cases of VME MCP Server?

  1. Creating and managing virtual machines using simple English commands.
  2. Automating VM provisioning in cloud environments.
  3. Load balancing and resource management in VME clusters.

FAQ from VME MCP Server?

  • Can I use any terminology for commands?

Yes! The server supports flexible terminology for commands.

  • What are the prerequisites for using VME MCP Server?

You need to have Claude Code CLI installed, Node.js, and access to an HPE VME instance.

  • How does the intelligent distribution feature work?

It automatically balances the load across cluster nodes based on your VM provisioning commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
frippe75
Star
0
Language
JavaScript
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