vcf-orchestrator-mcp
Related Servers
Alternatives to vcf-orchestrator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLets 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
- FlicenseBqualityNot gradedmaintenanceBridges Claude Code to a Cloud Orchestrator API, providing access to multi-AI consensus, web search, code execution sandboxes, long-term memory, knowledge graphs, deployment management, and 20+ integrated AI and developer tools.28-
- AlicenseAqualityDmaintenanceEnables 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.34Apache 2.0
- AlicenseBqualityCmaintenanceEnables 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.129 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
- AlicenseCqualityCmaintenanceEnables 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.500469 npmMIT
TDQS
Scored across 17 tools
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.
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.
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.
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.