vcf-automation-mcp
Related Servers
Alternatives to vcf-automation-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables LLM clients to browse and manage VCF Automation projects, catalog items, and deployments through MCP tools, including provisioning, day-2 actions, and deleting infrastructure.-

CloudGridofficial
AlicenseBqualityAmaintenanceDeploy or publish a web page or app from your AI assistant: CloudGrid plugs it and gives you a live URL. Apps can use managed MongoDB, Redis, pgvector, persistent disk, scheduled jobs, and an AI gateway that needs no API key. Use the hosted server at https://mcp.cloudgrid.io/mcp (Streamable HTTP, OAuth sign-in); there is nothing to install. Setup per client: https://docs.cloudgrid.io238820 npm1MIT- AlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with generated REST API services by exposing MCP tools and resources for CRUD operations, listing, and retrieval. It lets AI clients discover and call create, update, delete, list, and get-by-id actions against the same data available over REST.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to design, test, verify, install, and export REST-based management packs for VCF Operations without relying on the built-in AI Assistant.26MIT
- AlicenseAqualityBmaintenanceGoverned AI-ops MCP server for Nutanix Prism Central v4 REST API, offering 47 read/write tools for clusters, VMs, storage, network, catalog, data protection, alerts, and LCM upgrades with built-in audit, budget, and risk-tier governance.51MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and invoke tools generated from existing OpenAPI-described REST APIs through a governed MCP gateway with centralized authentication, policy-based access control, rate limiting, PII redaction, auditing, and token-efficient progressive discovery.MIT
TDQS
Scored across 698 tools
The 698-tool surface contains many overlapping or duplicate-looking operations across services: for example iaas_get_deployments vs deployment_get_deployments, iaas_get_projects vs project_get_all_projects, multiple cloud-account CRUD variants, and deprecated identity endpoints duplicating provider/cloudapi tools. An agent will struggle to choose the correct endpoint without deep knowledge of VCF service boundaries.
Names are mostly snake_case and service-prefixed, but the verb conventions are highly inconsistent: get vs retrieve vs query vs list vs fetch, create vs post, update vs modify vs patch, and path-derived names such as provider_delete_1_0_0_sessions_by_id and provider_post_1_0_0_sessions. The mix of deprecated names, odd abbreviations, and generated endpoint labels makes selection unpredictable.
A 698-tool server is far beyond a reasonable tool surface for an agent-facing MCP server, even for a broad platform. The count includes many deprecated, admin, and duplicate endpoints that should be filtered or consolidated.
Coverage is extremely broad across IaaS, catalog, deployments, blueprints, ABX, approvals, identity/provider, projects, policy, onboarding, vRO, event broker, forms, and content. There are likely minor gaps and lifecycle inconsistencies, but the surface appears to cover most VCF Automation workflows.