The initial health check for the GitHub Workflow MCP server was a simple placeholder. This ticket covers the work to make it more robust and meaningful by incorporating the more detailed verification logic from the existing buildScripts/ai/verifyGhSetup.mjs script.
The new health check now verifies three critical conditions:
- That the
gh CLI is installed.
- That the CLI is authenticated.
- That the CLI version meets a minimum requirement.
This ensures that the server only reports as "healthy" if it is fully capable of performing its duties.
Acceptance Criteria
- The
ai/mcp/server/github-workflow/services/healthService.mjs file is updated.
- The
buildHealthResponse function now performs separate checks for gh installation, authentication, and version.
- The JSON response from the
/healthcheck endpoint now includes a more detailed githubCli object with separate booleans for installed, authenticated, and versionOk.
- The overall health status is set to
unhealthy if any of the checks fail, with a descriptive error message included in the response.
The initial health check for the GitHub Workflow MCP server was a simple placeholder. This ticket covers the work to make it more robust and meaningful by incorporating the more detailed verification logic from the existing
buildScripts/ai/verifyGhSetup.mjsscript.The new health check now verifies three critical conditions:
ghCLI is installed.This ensures that the server only reports as "healthy" if it is fully capable of performing its duties.
Acceptance Criteria
ai/mcp/server/github-workflow/services/healthService.mjsfile is updated.buildHealthResponsefunction now performs separate checks forghinstallation, authentication, and version./healthcheckendpoint now includes a more detailedgithubCliobject with separate booleans forinstalled,authenticated, andversionOk.unhealthyif any of the checks fail, with a descriptive error message included in the response.