CI/CD MCP

Pipeline diagnostics, release gates, and workflow analysis

CI/CD MCP diagnoses delivery pipelines, evaluates release gates, and exports pipeline architecture through the hosted catalog.

Included with an active usage plan

Available through the hosted catalog. Calls count against the shared allowance on the account plan.

Compare usage plans

Why it exists

Diagnose pipeline failures and delays, evaluate release gates, and trace how delivery changes affect downstream systems.

Generic terminals, provider APIs, and custom prompts can cover parts of the work, but the caller must supply permission limits, output requirements, failure handling, and usage accounting.

Connection and contract

Connect from an MCP-aware client with an account-scoped Monarchic key. The hosted route checks access, runs the named product contract, and records the operation on the account receipt.

The product-specific schema defines the inputs and outputs used by clients and downstream automation.

Current limits

Live pipeline collection is a separate operation and requires a request-scoped read credential.

Requires an authenticated, entitled account. The demonstration call needs no GitHub, GitLab, or cloud credential.

What you get

Diagnose failed and slow pipeline runs
Evaluate release readiness from provider state
Export pipeline graphs for architecture analysis

Core use case

Diagnose pipeline failures and delays, evaluate release gates, and trace how delivery changes affect downstream systems.

Outcomes

Find queue delays, cache misses, false dependencies, and critical-path bottlenecks
Evaluate release readiness against live provider state
Export pipeline architecture for change-impact analysis

Primary workflows

Pipeline diagnosis Release gates Change impact Architecture export

Concrete workflow / priced call

Diagnose a delivery pipeline from supplied run data

The request, exact tool-call payload, returned output, and usage receipt are shown below.

Request

“Show me the likely bottlenecks and release risks in the demo pipeline.”

Execution

Tool call payload

{
  "tool": "diagnose_pipeline_run",
  "arguments": {}
}

Runs the deterministic demonstration diagnosis and returns stage, dependency, and release-gate findings without contacting a provider.

Output

Representative contract excerpt

{
  "contract": "cicd-mcp.pipeline-diagnosis.v1",
  "status": "complete",
  "findings": [
    "critical-path stage identified",
    "release requirement missing"
  ],
  "providerCalls": 0
}

Usage rating

At runtime

Recorded on the operation receipt

The diagnosis receives a measured receipt. Allowance quantities remain unpublished until the fully allocated rate card is frozen.