Skip to main content
Glama

Related Servers

Alternatives to vcf-orchestrator-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI assistants operate VMware Cloud Foundation 9.x environments (SDDC Manager, vCenter, NSX, VCF Operations, and experimental Automation/Orchestrator) without exposing VCF credentials or raw infrastructure APIs to the language model. It filters tools per user, enforces dry runs and signed human approvals for changes, and audits every call.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude to read and control Veeam Backup & Replication infrastructure through natural language, supporting full operator capabilities like starting/stopping jobs, creating backups, and monitoring threat detection via the VBR REST API.
      34
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables Claude Desktop to interact with enterprise REST APIs such as Jira, Zoho CRM, Salesforce, SharePoint, Procore, HxGN EAM, and Primavera P6 using OpenAPI/Swagger definitions, with support for various authentication workflows.
      12
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to discover and call any REST API from an OpenAPI/Swagger spec or Postman collection at runtime, with authentication, workflows, and prebuilt registry support.
      10 npm
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to call VCF Automation 9 REST operations as individual tools across 16 services, including deployments, catalog items, blueprints, policies, and IaaS resources. It also supports service-account setup, automatic token refresh, read-only filtering, and selective service loading.
      500
      469 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets (find/get/save/run for workflows and actions, executions, API spec). Minor overlap between vro_run_workflow (which waits and returns state) and vro_get_execution, and between vro_run_action and vro_run_script, but descriptions clarify the intended use of each.

    Naming Consistency5/5

    Every tool follows the same vro_<verb>_<noun> snake_case pattern (vro_api_search, vro_find_workflows, vro_save_action, vro_run_execution-style verbs). No mixed conventions or vague verbs, making the set highly predictable.

    Tool Count4/5

    17 tools for a broad platform (workflows, actions, executions, versions, and full REST API access) is reasonable and each tool earns its place. It leans slightly heavy, but the scope (full Orchestrator domain) justifies it.

    Completeness4/5

    Strong lifecycle coverage: find/get/save/run/delete for workflows, find/get/save/run for actions, plus execution inspection, version management, and a raw vro_api_call escape hatch for anything missing. Minor gaps exist (no delete action, no cancel/delete execution tool), workable via the generic API call.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues