vD vDan VMware · VCF · NSX · K8S

VMware Skills MCP Mind Map

Short answer: this mind map shows the VMware MCP servers of the public vmware-skills organization on GitHub. The tree goes from product area to project, tool category and MCP tool. The areas are vSphere, VKS, NSX, VCF Operations, Horizon and Private AI. Every project shows its latest GitHub release and its PyPI version. It also says whether the server is read-only and how many tools it has. Links lead to the repository, the release notes and the package. VMware Monitor, the read-only vCenter and ESXi server, is expanded to all 33 of its MCP tools. Each tool shows its description, its parameters and the CLI command with the same data. It also shows the name the tool had before release 2.0. A line above the map says when the sources were last checked. It lists the releases and tools that are new since the previous check. Search project names, tool names, old names and descriptions. Filter by product area, read-only or PyPI. Export the selection as Markdown.

Prefer a full window? Open the mind map full screen →

How to use the VMware MCP servers mind map

  • Which project covers my task? Open a product area and read the project rows: one line each with the version, the release date, the tool count and whether the server is read-only. The panel adds the GitHub description, the README summary, the install command and the companion skills the project itself recommends.
  • What does the latest release offer? The project panel names the latest GitHub release with its title and date, the PyPI version with its upload date and the tool count the project states. The categories below it open to the tools; a tool of VMware Monitor shows its parameters with types and defaults, the CLI twin (for example get_cluster_health_summary and vmware-monitor summary) and a link to the source line at the release tag.
  • What changed since my last visit? The change line above the map compares the current check with the previous data file: new releases with the version jump, tools added, removed or renamed, and projects that could not be re-checked. A project with a new release carries a “new release” mark in the list.
  • Search, filters, links. The search matches project names, tool names, the names tools had before release 2.0, descriptions, parameters and CLI commands. “Only” narrows the tree to read-only servers, packages on PyPI or MCP servers; the area buttons keep one product area. “Copy link” writes a URL such as ?tool=get_cluster_health_summary or ?project=vmware-nsx that opens this page on that node. “Markdown” copies the current selection.

What the VMware MCP servers are

The vmware-skills repositories are community projects by a VMware engineer. They are not official VMware or Broadcom products. Each MCP server is a Python package on PyPI. It ships a SKILL.md for coding agents and a CLI with the same reads. VMware Monitor is read-only by construction. A test parses every source file and refuses any vSphere call outside a reviewed allowlist. The other servers write as well and state their read and write counts. The map shows those counts and the read-only statement of each README. Release 2.0 of the family renamed the tools so that every name starts with a verb. The map keeps the old names searchable and shows the rename on the tool.

Frequently asked questions

Which VMware MCP server is safe to point at production?

VMware Monitor, VMware Log Insight and VMware Harden list no write tools. VMware Monitor documents the enforcement: no power, create, delete, snapshot, clone or migrate function exists in its code, and a test fails if one is added. Pair it with a vCenter account that holds the built-in Read-Only role. The “read-only” filter of the map shows these three projects.

Where do the version and the tool count come from?

The version and the date come from the latest GitHub release of the repository and from the PyPI JSON of the package; the map shows both and flags a difference. The tool count is the number the README or the SKILL.md states, and the tools are parsed from their tables. For VMware Monitor the tools come from the MCP server sources at the release tag, so the count is traceable to the release.

How often is the map refreshed?

The data file is built by a script that reads GitHub and PyPI. The change line shows the date of the last check. The script diffs its output against the previous file, so every run reports what is new since the previous one.

What is a CLI twin?

Every VMware Monitor MCP tool has a command of the vmware-monitor CLI that returns the same data, for example vmware-monitor investigate vm <name> for the tool investigate_vm. The map shows the command with a copy button. Small local models are often better served by the CLI than by the MCP tool schemas.

Why are old tool names still in the map?

Release 2.0 of VMware Monitor renamed 23 of its tools, for example cluster_health_summary to get_cluster_health_summary, and the other servers did the same. A prompt, a workflow or a deny rule written with the old name no longer matches. The map keeps the old names searchable and the tool panel shows the rename with its release.

Sources