msclabs.devsecops-cicd-mcp-server
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
{
"mcpServers": {
"msclabs.devsecops-cicd": {
"command": "uvx",
"args": ["msclabs.devsecops-cicd-mcp-server@latest"]
}
}
}
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 401 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.
| Variable | Default | Purpose |
|---|---|---|
MCP_API_TOKEN |
— | Your API key. Required. |
MSCLABS_MCP_BASE_URL |
the CoE endpoint | Point at a different deployment. |
MSCLABS_MCP_TIMEOUT |
120 |
Seconds to wait for one call. |
Metadata
Release files for msclabs.devsecops-cicd-mcp-server 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| msclabs_devsecops_cicd_mcp_server-1.2.0.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| msclabs_devsecops_cicd_mcp_server-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / msclabs_devsecops_cicd_mcp_server-1.2.0.tar.gz
| Download URL | msclabs_devsecops_cicd_mcp_server-1.2.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d43850694df4d48f1c157ee8e990cc6cb1b7db1e9d6382c63fc5957b915bba86
|
|
BLAKE2b-256 checksum How to use checksums |
59cfcd818de70e15002c6e0dc60187a512e3f79914df0d344f2ad91a1b539f66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Release files / msclabs_devsecops_cicd_mcp_server-1.2.0-py3-none-any.whl
| Download URL | msclabs_devsecops_cicd_mcp_server-1.2.0-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
051043e0e66b58aeda9235f74f068752285d9a646efb1b44f4f1c8c48b568050
|
|
BLAKE2b-256 checksum How to use checksums |
3e451186ae1a5f50546ac7c2bc0bb1cfae868af68909d003fd7e4349b0297978
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for msclabs.devsecops-cicd-mcp-server 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.