vcf-super-cli (`vsc`)

A modern, agent-friendly CLI for VMware Cloud Foundation 9. The command tree is generated dynamically by introspecting the official vcf-sdk vAPI bindings — so the surface mirrors the real VCF 9 API instead of being hand-maintained.

$ vsc vsphere vm list --profile prod
$ vsc vsphere host get --host host-42
$ vsc nsx segments list --output table
$ vsc vsphere power stop vm-42 --apply        # writes are dry-run without --apply

⚠️ Alpha / pre-release. Reads (vSphere + NSX inventory) and writes are both available. Writes are dry-run by default — nothing changes without --apply, and a dry-run never opens a connection.

Why

Mirrors the real API. Commands come from the SDK's own vAPI metadata (VapiInterface services + OperationRestMetadata), covering both vCenter and NSX from one generator.
Modern. REST-first via vmware-vcenter, with pyVmomi as a fallback where REST lacks coverage.
Safe by default. Writes preview as dry-runs unless you pass --apply; a dry-run never opens a connection.
Agent-friendly. Deterministic command shape, machine-readable JSON output, a stable error envelope with documented exit codes, and a bundled agent Skill.

Scope

Area	Status
vSphere / vCenter read (`vsc vsphere …`)	✅ v0.1
NSX Policy API read (`vsc nsx …`)	✅ v0.1
Writes — dry-run by default + `--apply` (`vsc vsphere …` / `vsc nsx …`)	✅ v0.2
Ergonomics — offline shell completion, per-field filter flags + paging, pyVmomi fallback (`perf`/`events`/`tasks`/`inventory`)	✅ v0.3
Live resource-id completion	✅ v0.4
Find VMs by attribute — IP / hostname / MAC / guest OS / power (`vsc vsphere inventory find`)	✅ v0.5
NSX Traceflow — inject a synthetic packet, read its path (`vsc nsx traceflows` / `vsc nsx observations`)	✅ v0.6
NSX Manager / Global-Manager, SDDC Manager, Operations, LCM	deferred

Install

uv tool install vcf-super-cli      # recommended
# or
pipx install vcf-super-cli
# or
pip install vcf-super-cli

From source:

uv sync && uv run vsc --help

Documentation

Full guide: thomaschristory.github.io/vcf-super-cli

License

Apache-2.0. See LICENSE.

Metadata

Release files for vcf-super-cli 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vcf-super-cli 0.6.0
File	Size	Uploaded
vcf_super_cli-0.6.0.tar.gz	176.1 kB	Jul 3, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for vcf-super-cli 0.6.0
File	Interpreter	ABI	Platform	Reset
vcf_super_cli-0.6.0-py3-none-any.whl 63.8 kB Jul 3, 2026	Python 3	none	any	Details

Total release size: 240.0 kB

Release files / vcf_super_cli-0.6.0.tar.gz

Download URL	vcf_super_cli-0.6.0.tar.gz
Size	176.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`d9405521915fec97746d461214f4bbe9769b8c4eeb82e3cc8b08192f78fe3a8e`
BLAKE2b-256 checksum How to use checksums	`c856fd1379058fb84247dc1bcef98bea39e763a08bd4f7d9efdfb29058d31a58`
Upload date	Jul 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.12`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/thomaschristory/vcf-super-cli
Publishing commit: github.com/thomaschristory/vcf-super-cli/tree/6b8ac0286dbd43137dcd1b71251e409e30c62546

Workflow

Publishing configuration: github.com/thomaschristory/vcf-super-cli/blob/6b8ac0286dbd43137dcd1b71251e409e30c62546/.github/workflows/release.yml
Publishing logs: github.com/thomaschristory/vcf-super-cli/actions/runs/28683280106/attempts/1

Artifact

Subject: vcf_super_cli-0.6.0.tar.gz
SHA-256 checksum: d9405521915fec97746d461214f4bbe9769b8c4eeb82e3cc8b08192f78fe3a8e Verifying attestations

Release files / vcf_super_cli-0.6.0-py3-none-any.whl

Download URL	vcf_super_cli-0.6.0-py3-none-any.whl
Size	63.8 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`b65609ebdca8496fe700a6dfc9dd5f78e5cf1f5069889ffbe7f8ffbefc34729c`
BLAKE2b-256 checksum How to use checksums	`887485faa2308bce310f832272b8020e520e20e2f74003f64411b28675353f16`
Upload date	Jul 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.12`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/thomaschristory/vcf-super-cli
Publishing commit: github.com/thomaschristory/vcf-super-cli/tree/6b8ac0286dbd43137dcd1b71251e409e30c62546

Workflow

Publishing configuration: github.com/thomaschristory/vcf-super-cli/blob/6b8ac0286dbd43137dcd1b71251e409e30c62546/.github/workflows/release.yml
Publishing logs: github.com/thomaschristory/vcf-super-cli/actions/runs/28683280106/attempts/1

Artifact

Subject: vcf_super_cli-0.6.0-py3-none-any.whl
SHA-256 checksum: b65609ebdca8496fe700a6dfc9dd5f78e5cf1f5069889ffbe7f8ffbefc34729c Verifying attestations