aap-mcp-validator

To validate AAP MCP server connectivity, you run a specific check to verify that required Agile Access Proxy Control Plane servers are available and reachable before executing automated skills. This prevents server connection issues during your automation workflows.

Automated skill execution fails because required AAP MCP servers may be inaccessible or offline. Running a server connectivity check beforehand validates that specified servers are reachable, ensuring automation processes proceed smoothly without unexpected connection drops.

To check access for a governance assessment, execute the server validation skill with the servers parameter set to governance_assessment. This verifies all required AAP MCP servers are accessible before proceeding with governed workflow execution.

Yes, you can validate specific servers depending on your skill requirements. The validation process checks accessibility for different servers needed across various use cases including job management, inventory handling, configuration management, security, system monitoring, and user management.

Server validation checks are needed as the first step in governed workflows before executing any skills that require AAP MCP access. Running this automated verification step ensures all necessary servers are available before proceeding with automation tasks.

Yes, AAP MCP server validation supports connectivity checks across workflows involving job templates, inventories, notification templates, credentials, instance groups, and users. This ensures all required dependent components are accessible before automation execution begins.