Fix MCP Gateway v0.0.47+ schema validation in metrics-collector workflow

[Copilot]

The Metrics Collector workflow was failing with schema validation errors after MCP Gateway v0.0.47 changed from HTTP-based to container-based stdio configuration for GitHub MCP servers.

Changes

• Removed mode: remote from .github/workflows/metrics-collector.md frontmatter
• Recompiled workflow to generate stdio-based MCP configuration with container image

Before/After

Before (HTTP mode, deprecated):

"github": {
  "type": "http",
  "url": "https://api.githubcopilot.com/mcp/",
  "headers": {
    "Authorization": "Bearer ${GITHUB_PERSONAL_ACCESS_TOKEN}",
    "X-MCP-Lockdown": "...",
    "X-MCP-Readonly": "true",
    "X-MCP-Toolsets": "context,repos,issues,pull_requests"
  }
}

After (stdio mode, v0.0.47+ compatible):

"github": {
  "type": "stdio",
  "container": "ghcr.io/github/github-mcp-server:v0.28.1",
  "env": {
    "GITHUB_LOCKDOWN_MODE": "$GITHUB_MCP_LOCKDOWN",
    "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_MCP_SERVER_TOKEN}",
    "GITHUB_READ_ONLY": "1",
    "GITHUB_TOOLSETS": "context,repos,issues,pull_requests"
  }
}

Removing mode: remote allows the compiler to default to stdio mode with container-based configuration, matching the schema required by MCP Gateway v0.0.47+.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[P1] Metrics Collector Failing - MCP Gateway Schema Validation Error</issue_title>
<issue_description># 🚨 High Priority: Metrics Collector Workflow Failing

Summary

The Metrics Collector workflow has degraded to 50% success rate (5/10 runs) starting January 9, 2026. This is blocking all workflow health monitoring and metrics collection.

Error Details

• Error Type: MCP Gateway configuration validation error
• MCP Gateway Version: v0.0.47
• Success Rate: 50% (was 100% before 2026-01-09)
• Last Success: Run Add HTTP transport capability validation and time MCP server for agentic engines #19 (2026-01-08)
• Impact: No workflow metrics collected for 5+ days

Root Cause

MCP Gateway schema breaking change in v0.0.47 requires:

• New container property for stdio server config
• Removal of command property (now invalid)
• Updated configuration structure

Error Messages

Error: failed to load config: Configuration validation error (MCP Gateway version: v0.0.47):
Error: doesn't validate with mcp-gateway-config.schema.json#
  Error: doesn't validate with '/definitions/mcpServerConfig'
    Error: oneOf failed
      Error: doesn't validate with '/definitions/stdioServerConfig'
        Error: missing properties: 'container'
        Error: additionalProperties 'command' not allowed

Sample Failed Run

• Run: https://github.com/githubnext/gh-aw/actions/runs/20960733354
• Date: 2026-01-13
• Run Number: githubnext/gh-aw#24

Required Fix

Update MCP Server Configuration

The workflow needs to migrate from old schema:

tools:
  server_name:
    command: "/path/to/server"
    args: ["--arg1"]
    env:
      VAR: "value"

To new schema:

tools:
  server_name:
    container:
      image: "server-image:latest"
      # or for stdio mode
      # command: "/path/to/server"
      # args: ["--arg1"]
    env:
      VAR: "value"

Recommended Actions

Immediate (P1)

1. Review Workflow File: .github/workflows/metrics-collector.md
2. Update MCP Configuration: Migrate to new schema format
3. Test with MCP Gateway v0.0.47: Validate configuration
4. Recompile Workflow: Run make recompile after changes

Follow-up

1. Audit all workflows for MCP Gateway usage
2. Document schema migration guide
3. Add schema validation to CI/CD
4. Consider pinning MCP Gateway version

Impact Assessment

Direct Impact

• No workflow metrics since 2026-01-09
• Workflow Health Manager lacks execution data
• Agent Performance Analyzer missing metrics
• Unable to track success rates, failures, performance

Cascade Impact

• Meta-orchestrator monitoring degraded
• System health visibility lost
• Other orchestrators (Campaign Manager) affected
• Cannot detect new failures or trends

Related Issues

• Part of MCP Gateway breaking change affecting multiple workflows
• Meta-orchestrator cascade failure
• Highest priority for system visibility restoration

Detection

Identified by Workflow Health Manager on 2026-01-14
Health Score Impact: -10 points (75/100 overall)

---

Labels: workflow-health, priority-p1, type-failure, mcp-gateway
Related Workflows: Agent Performance Analyzer, Workflow Health Manager

AI generated by Workflow Health Manager - Meta-Orchestrator

Comments on the Issue (you are @copilot in this section)

• Fixes [P1] Metrics Collector Failing - MCP Gateway Schema Validation Error #9898

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.