Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    VCF Operations Orchestrator 9.x with vcf-orchestrator-mcp

    1

    Manage and execute VCF Operations Orchestrator workflows and actions via MCP.

    Free

    1 useSecurity scanned
    VCF Operations Orchestrator 9.x with vcf-orchestrator-mcp

    VCF Operations Orchestrator 9.x with vcf-orchestrator-mcp

    Example session with this skill installed

    Build a vRO workflow that checks whether a VM is powered on and returns a short report. Do a dry run first.

    • Read your context and instructions
    • Compiled the vcf operations orchestrator

    Done. The workflow is built, validated with a dry run, saved, and tested.

    I created the

    Report VM Power State workflow (version

    1.0.0) in the Lab/Utilities folder. It finds a vCenter VM by its exact name, reads its power state, and returns a one-line report.

    First I ran a

    dry run: it generated and validated the full workflow without saving anything. The structure was correct, so I saved it and tested it on two VMs.

    Workflow structure

    #StepTypeReadsWrites
    1Find VMScriptvmNamevm
    2Read power stateScriptvmpowerState
    3Powered on?DecisionpowerStategoes to 4 or 5
    4Report onScriptvmNamereport
    5Report offScriptvmName, powerStatereport
    6EndEnd

    Inputs and outputs

    NameTypeKind
    vmNamestringInput: exact VM name in vCenter
    reportstringOutput
    vmVC:VirtualMachineAttribute
    powerStatestringAttribute

    Scripts

    All scripts are plain ES5 for Orchestrator's Rhino engine.

    Find VM

    var found = VcPlugin.getAllVirtualMachines(null, "xpath:name='" + vmName + "'");
    if (!found || found.length === 0) { throw "VM not found: " + vmName; }
    vm = found[0];
    System.log("Found " + vm.name);
    

    Read power state

    powerState = vm.runtime.powerState.value;
    

    Powered on? (decision)

    return powerState === "poweredOn";
    

    Report on

    report = vmName + " is powered on";
    

    Report off

    report = vmName + " is not powered on (" + powerState + ")";
    

    Test results

    RunInputStateOutput report
    Dry runnoneValidated, not savednone
    1web01Completedweb01 is powered on
    2test01Completedtest01 is not powered on (poweredOff)

    Next steps

    • Report on many VMs: I can add an Array/string input and loop over it, as version 1.1.0.

    Use it in other workflows: I can move the lookup into a reusable action, such as getVmByName, and call it from this workflow and others.

    Your naming convention: if your team has a standard for folder and workflow names, tell me and I'll rename or move it.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Working with VCF Operations Orchestrator (vRO) from an AI agent is powerful, but only if the agent knows the platform. This free skill pairs with the open-source vcf-orchestrator-mcp server and teaches your agent how to use it well.

    What your agent learns

    Which tool to use for each job: find and read workflows, run them, investigate failed runs, create and update actions and workflows, run quick scripts, and reach the full Orchestrator REST API (300+ operations) for packages, configuration elements and more. Orchestrator’s rules: every script in plain ES5 for the Rhino engine, no hard-coded credentials, and versions bumped on every change. A safe way of working: read before changing, build and test in small steps, dry run before anything that touches infrastructure, confirm before deleting, and fix failures from the actual error and logs. How to set up and troubleshoot the connection to VCF Automation 9: service account setup, roles, token refresh, and the common 401 and permission problems.

    What’s included: SKILL.md, a setup and troubleshooting guide, a tool reference, the workflow spec format with a complete example, and a worked example of building, testing and fixing an action.

    Works with: VCF Operations Orchestrator 9.x, embedded in VCF Automation 9 or standalone.

    Requires: Node.js 18.17+, the vcf-orchestrator-mcp server (npm install -g vcf-orchestrator-mcp), and a VCF Automation 9 org with a local admin user. The skill contains instructions only: no scripts, no binaries, no credentials.

    Requires vcf-orchestrator-mcp server setup. Limited to ES5 JavaScript syntax due to Orchestrator's Rhino engine. Does not handle password/token entry via chat.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Node.js
    Vcf Orchestrator MCP

    Permissions

    Network Access
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill bridges the gap between AI agents and VMware Cloud Foundation (VCF) by providing a direct interface to the vRO API, allowing you to manage workflows and actions without manually navigating the legacy vRO client.

    The skill is designed for any AI agent or interface that supports the Model Context Protocol (MCP), such as Claude Desktop or other MCP-compatible IDEs, provided the vcf-orchestrator-mcp server is running.

    Because vRO uses the legacy Rhino engine, this skill enforces ES5 syntax rules and handles complex JSON-to-vRO type mappings, preventing the silent failures that occur when using modern ES6+ JavaScript.

    You must have the vcf-orchestrator-mcp NPM package installed and configured to point to your VCF Operations Orchestrator 9.x instance, including valid authentication credentials.

    Yes, the skill includes tools to query plug-in objects, such as `VC:VirtualMachine` or `VRA:Host`, enabling you to find specific resource IDs required for workflow inputs.

    The skill provides real-time execution monitoring, allowing you to trigger workflows and immediately retrieve logs and execution states to troubleshoot infrastructure tasks.

    New in Workflow Automation