SSyncDev

VMware vSphere MCP Server

Read-only vCenter inventory for migration planning: blockers, snapshots, per-core licence exposure

Local serverstdio

What is the VMware vSphere MCP Server?

VMware vSphere MCP is an MCP integration. Read-only vCenter inventory for migration planning: blockers, snapshots, per-core licence exposure.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/vsphere-v0.1.5/vsphere-mcp.mcpb, version 0.1.5. Its declared MCP transport is stdio.

The package declares VSPHERE_PASSWORD (required): Password for VSPHERE_USERNAME.; VSPHERE_USERNAME (required): vCenter SSO user, for example readonly@vsphere.local. A Read-Only role is enough.; VSPHERE_BASE_URL (required): Your vCenter, https:// (https only).; VSPHERE_TLS_FINGERPRINT: Optional. Only for a self-signed vCenter certificate: its SHA-256 fingerprint (comma-separate several).; VSPHERE_USER_AGENT: Optional. Overrides the User-Agent the CLI sends to vCenter. Leave blank to use the built-in one.; PRINTING_PRESS_CLIENT_PROFILE: Optional. Binds the MCP server to one saved client profile. Leave blank for the default.; VSPHERE_MCP_READ_ONLY: Optional. Set to exactly 1 to expose only read-only tools. vCenter is only ever read; the tools that write this CLI's own files (learnings, playbooks, the local store, exports) act only with confirm set to true, and this switch hides them. Leave blank.; VSPHERE_NO_LOCAL_DATA: Optional. Set to 1 to keep no local copy of API responses: reads go to vCenter and nothing is written to the local store. Leave blank to keep the local store.; VSPHERE_MCP_HTTP_TOKEN: Required only when running the MCP server with --transport http (a remote/hosted deployment). Callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport that Claude Desktop uses..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.5 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
VSPHERE_PASSWORDPassword for VSPHERE_USERNAME.Yes
VSPHERE_USERNAMEvCenter SSO user, for example readonly@vsphere.local. A Read-Only role is enough.Yes
VSPHERE_BASE_URLYour vCenter, https:// (https only).Yes
VSPHERE_TLS_FINGERPRINTOptional. Only for a self-signed vCenter certificate: its SHA-256 fingerprint (comma-separate several).Check documentation
VSPHERE_USER_AGENTOptional. Overrides the User-Agent the CLI sends to vCenter. Leave blank to use the built-in one.Check documentation
PRINTING_PRESS_CLIENT_PROFILEOptional. Binds the MCP server to one saved client profile. Leave blank for the default.Check documentation
VSPHERE_MCP_READ_ONLYOptional. Set to exactly 1 to expose only read-only tools. vCenter is only ever read; the tools that write this CLI's own files (learnings, playbooks, the local store, exports) act only with confirm set to true, and this switch hides them. Leave blank.Check documentation
VSPHERE_NO_LOCAL_DATAOptional. Set to 1 to keep no local copy of API responses: reads go to vCenter and nothing is written to the local store. Leave blank to keep the local store.Check documentation
VSPHERE_MCP_HTTP_TOKENRequired only when running the MCP server with --transport http (a remote/hosted deployment). Callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport that Claude Desktop uses.Check documentation