Skip to main content
Glama
Sign In
vmware-pilot

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
      D
      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
      -

    • workflow-sm

      pirate-liuzz
      A
      license
      Not graded
      quality
      C
      maintenance
      A stateful MCP workflow engine that enforces strict step ordering for AI agents, persisting run state so interrupted workflows can be resumed from a checkpoint. It also supports parallel step groups, bounded retries, agent-chosen jumps between steps, rewinding, and a live browser dashboard across any MCP client.
      1
      MIT

    • 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.
      27 npm
      23
      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.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct lifecycle phases (design, draft, confirm, run, approve, cancel, rollback) and descriptions explicitly cross-reference each other to guide selection, e.g. cancel only stops future steps while rollback reverses completed ones. The residual ambiguity is the three creation entry points (create_workflow, create_workflow_from_template, design_workflow), which all start a workflow but are differentiated by intent (known steps, matching template, or a goal).

    Naming Consistency4/5

    The set mostly follows a predictable verb_noun pattern (cancel_workflow, run_workflow, create_workflow, review_workflow, update_draft, list_workflows). Two runtime gates break the pattern with bare verbs (approve, rollback) and get_workflow_status is verb_noun_noun, but these are minor, still-readable deviations.

    Tool Count5/5

    13 tools is well-scoped for a workflow orchestration server; each maps to a distinct lifecycle action (create/design/draft/confirm/review/run/approve/cancel/rollback/status/list/catalog). No redundant or filler tools.

    Completeness5/5

    The surface covers a full workflow lifecycle: discovery (list_workflows, get_skill_catalog), authoring (design_workflow, create_workflow, create_workflow_from_template, update_draft), validation (review_workflow), gating/execution (confirm_draft, run_workflow, approve), and termination (cancel_workflow, rollback), plus status. The only arguable gap is a hard delete for abandoned drafts, which cancel/terminal-state handling largely covers.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources