Overview In our 25.3 launch, we added an MCP server to implement AI into release orchestration processes. Learn more about how it's helping users!
What it is An AI-aware control plane for Release that lets you create/search/manage releases, design templates, tune gates, and analyze failures in one place. It works with existing Release features and integrations.
General use cases (problem → solution)
Triage time is slow → Use natural-language queries (“show promotions that failed perf_gate in prod in last 24h”) to retrieve the runs, logs, artifacts, and failing conditions; generate remediation steps.
Policy drift across teams → Define promotion/gate/evidence policies once in shared templates; MCP helps find projects on old versions and prompts upgrades.
Inconsistent integrations/variables → Standardize Jenkins/Jira/Git connections and variable schemas at folder/template scope; block promotion if required variables are missing.
Unclear audit trail → Query releases by gate, owner, or risk; export evidence (inputs, checks, approvals) from one place.
Develop a greater understanding of how to implement the MCP server from our documentation, which you can see here: https://docs.digital.ai/release/docs/how-to/release-mcp-server