aidlc.devsecops-cicd-mcp

Connects an MCP client to the AI-DLC DevSecOps CI/CD deploy workflow, which runs in the MSC Labs CoE account. The workflow, its guardrails and its policy live there; this package is only the stdio bridge.

Configure

Track the latest release:

{
  "mcpServers": {
    "aidlc.devsecops-cicd": {
      "command": "uvx",
      "args": ["aidlc.devsecops-cicd-mcp@latest"],
      "env": { "MCP_API_TOKEN": "${MCP_API_TOKEN}" }
    }
  }
}

Or pin one, so a new release reaches your machine only when you change the number:

"args": ["aidlc.devsecops-cicd-mcp==1.0.0"]

Set MCP_API_TOKEN to the key the CoE issued you, and add MCP_API_TOKEN to your client's approved environment variables. Without a key the registry answers 403 and nothing works.

What it does not do

It holds no copy of the workflow, caches nothing and decides nothing. Every step, reference and policy check is answered by the hosted server at call time, so what you run is always what the CoE published.