vCenter-mcp-server

Created By
lijian-uia year ago
Overview

what is vCenter-mcp-server?

vCenter-mcp-server is a tool designed specifically for vCenter Server, aimed at simplifying virtual machine management tasks. It provides an efficient interface for operations such as virtual machine migration and querying through seamless integration with vCenter Server.

how to use vCenter-mcp-server?

To use vCenter-mcp-server, clone the project code from the repository, install the required dependencies, modify the configuration file with your vCenter Server connection details, and run the server using the recommended command.

key features of vCenter-mcp-server?

  • Stable connection to vCenter Server for comprehensive access to the virtualization environment.
  • Virtual machine migration capabilities, allowing users to migrate single or multiple virtual machines between hosts.
  • Detailed querying of virtual machine information to quickly understand the status of VMs.

use cases of vCenter-mcp-server?

  1. Migrating virtual machines between different hosts.
  2. Querying detailed information about virtual machines on a host.
  3. Managing virtual machine lifecycle operations such as creation and shutdown.

FAQ from vCenter-mcp-server?

  • What is the primary function of vCenter-mcp-server?

It simplifies the management of virtual machines by providing tools for migration and information querying.

  • Is there a cost associated with using vCenter-mcp-server?

No, it is open-source and free to use.

  • What programming language is vCenter-mcp-server written in?

It is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lijian-ui
Star
0
Language
Python
License
Apache-2.0 license
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago