Release Management

Short answer

Load release catalog and gate-oriented details with get_release / get_release_details, and push scanner results with report_*_findings and update_scan_progress. Auth is the project API key only.

Common scenarios

CI quality gate

1. Call getReleaseDetails with { "version": "<label>" }.
2. Apply your policy on summary.environmentStats, summary.issueStats, and summary.scanSummaries.

See the full curl/jq example in Programmatic release gating.

Agent / ExploreChimp targeting

Use getRelease for the thin catalog (SHA, prior release, focus areas).

Security scan reporting

Step	Operation
Load scan config	getSecurityScanConfig
Progress	updateScanProgress
Findings	reportDastFindings, reportSastFindings, reportSecretsFindings, reportDepsFindings

Related

• API Basics
• Interactive API Reference

Frequently asked questions

Which endpoint gates CI?

POST /api/mcp/get_release_details with { version }. Apply your own policy on the returned summary and detail.

Related pages

• Release Management
• Issue Management
• Release Checks