Skip to main content
Glama
vmware-skills

vmware-pilot

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vmware-pilot

No user-submitted related servers found.

    Related Servers

    • skills-over-mcp

      hemanth
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables multi-step, opinionated workflows (skills) as MCP resources with lazy loading, encoding team knowledge like branch naming and test procedures alongside tool execution.
      3
      -

    • vsphere-mcp-extended

      999yurik666
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables VMware vCenter management via MCP, adding real-time and historical performance monitoring, VM lifecycle operations, snapshots, ISO mounting, and network/host management through natural language.
      MIT

    • mcpGraph

      TeamSparkAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables orchestration of MCP tool calls through declarative YAML-defined directed graphs with data transformation, conditional routing, and observable execution flows.
      221 npm
      22
      MIT

    • vmware-harden

      vmware-skills
      A
      license
      A
      quality
      A
      maintenance
      VMware vSphere compliance and hardening — read-only baseline scanning plus drift detection across CIS, DISA STIG, vSphere SCG, China DJCP 2.0, and PCI-DSS frameworks. Includes LLM-powered remediation suggestions; apply-side gated through the vmware-pilot approval workflow.
      8
      205 PyPI
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct lifecycle stage or concern: design/update/confirm for drafts, plan/create for different workflow origins, run/approve/cancel/rollback for execution control, and list/review/status/catalog for inspection. The overlapping creation tools (design_workflow, plan_workflow, create_workflow) are clearly separated by input type and use case.

    Naming Consistency4/5

    Most tools follow verb_noun (design_workflow, update_draft, get_workflow_status, confirm_draft, cancel_workflow, list_workflows, review_workflow, run_workflow), with a few single-word verbs (approve, rollback) that still read clearly in context. The convention is consistent enough that an agent can predict tool purpose from the name.

    Tool Count5/5

    13 tools cover the full workflow lifecycle without redundancy. Each tool earns its place: creation (3 variants), editing/confirmation, execution control, and inspection. The count feels well-scoped for a workflow orchestration server.

    Completeness5/5

    The tool surface covers the entire lifecycle: design → update → confirm → review → run → approve/cancel/rollback, plus discovery (list_workflows, get_skill_catalog) and monitoring (get_workflow_status). There are no obvious dead ends, and the refusal/error paths explicitly name remediation actions (e.g., adding approval gates).

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources