VMware AIops vs VMware Pilot
A side-by-side look at the VMware AIops and VMware Pilot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose VMware AIops for cloud platforms work as a local process; choose VMware Pilot for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose VMware AIops when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
Choose VMware Pilot when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_skill_catalog, list_workflows, review_workflow.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 44/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 77 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 13 |
| Full listing | View VMware AIops | View VMware Pilot |
Tools & capabilities
VMware AIops tools
No tool names declared yet. Check the project README from the listing page.
VMware Pilot tools 13
get_skill_catalogList all available skills and tools for workflow designlist_workflowsList built-in and custom templatesreview_workflowSanity-check a planned workflow before executiondesign_workflowNatural language goal → draft workflowupdate_draftEdit draft workflow stepsconfirm_draftFinalize draft → ready to executecreate_workflow_from_templateCreate and save a workflow from a template (not a dry run), returns workflow_idcreate_workflowCreate custom workflow from step list (refused if a destructive step has no approval gate before it)run_workflowExecute workflow, pauses at approval gatesget_workflow_statusQuery state + diff report + audit logapproveHuman approval, continue executionrollbackExplicit, best-effort undo of steps pilot recorded as succeeded — never automatic. Previews (`blast_radius`) unless `confirm=True- +1 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
VMware AIops
{
"mcpServers": {
"vmware-aiops": {
"command": "uvx",
"args": [
"--from",
"vmware-aiops",
"vmware-aiops"
]
}
}
}
VMware Pilot
{
"mcpServers": {
"vmware-pilot-2": {
"command": "uvx",
"args": [
"vmware-pilot"
]
}
}
}
Frequently asked questions
VMware AIops is categorized under Cloud Platforms and uses a local stdio subprocess. VMware Pilot belongs to Cloud Platforms and uses a local stdio subprocess. Pick VMware AIops for cloud platforms work and VMware Pilot for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
VMware AIops has no declared pricing — check the project's own site. VMware Pilot has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add vmware-aiops and vmware-pilot-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, VMware AIops has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 77 GitHub stars. VMware Pilot has 53/100 (Good) with 0 views, 0 installs and 4 GitHub stars.