MCP Metrics Build and Deploy Flow¶

This diagram shows the CI/CD path that currently exists for the deployable metrics server and its Azure Container Apps target.

Source files: .github/workflows/mcp-build.yml, .github/workflows/mcp-deploy.yml, infra/mcp/main.bicep

1. CI and deployment flow¶

flowchart TD
    A["Change touches<br/>mcp/basecoat-metrics/**<br/>infra/mcp/**<br/>or MCP workflows"] --> B["mcp-build.yml"]
    B --> C["Validate runner routing contract"]
    C --> D["npm ci + npm run build<br/>mcp/basecoat-metrics"]
    D --> E["Docker smoke build"]
    E --> F["az bicep build<br/>infra/mcp/main.bicep"]
    F --> G{"Merged to main or workflow_dispatch?"}

    G -->|No| H["PR validation ends here"]
    G -->|Yes| I["mcp-deploy.yml"]
    I --> J["Resolve deploy runner + log in to GHCR"]
    J --> K["Build and push<br/>basecoat-metrics-mcp image"]
    K --> L["Operation-context policy preflight"]
    L --> M["Environment drift gate"]
    M --> N["Azure ARM deploy<br/>infra/mcp/main.bicep"]
    N --> O["Azure Container Apps<br/>MCP_TRANSPORT=http<br/>NODE_ENV=production"]
    O --> P["Verify running revision"]
    P --> Q["Smoke test<br/>GET /health"]
    Q --> R["Publish FQDN and MCP endpoint"]

2. Reading guide¶

mcp-build.yml is the fast feedback gate: compile TypeScript, build the Docker image once, and lint the Bicep template.
mcp-deploy.yml turns a successful main-branch or manual run into a GHCR image, then deploys that image through infra/mcp/main.bicep after policy and drift checks pass.
The container app is configured for HTTP ingress only, which is why the deployed metrics service exposes /health and a shared remote MCP endpoint.

3. Scope note¶

The deploy flow above applies to basecoat-metrics. The root mcp/ package remains a local stdio package with a Docker wrapper and self-test, but it is not deployed by mcp-build.yml or mcp-deploy.yml in the current repository layout.