ReleaseOps MCP

Release checks and reviewer handoff

ReleaseOps MCP turns release readiness into structured checks, manifests, changelog scope, and a reviewer handoff pack.

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

Turn release readiness into structured checks and exportable review artifacts.

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

The receipt hash detects changed output; it is not a signature. This call does not independently inspect the repository or create a tag.

No repository, provider, network, subprocess, or mutation access is used. The caller supplies the facts to check.

What you get

Evaluate release readiness
Catch missing documentation and artifacts
Export a reviewable release pack

Core use case

Turn release readiness into structured checks and exportable review artifacts.

Outcomes

Catch documentation drift and missing release artifacts
Prepare a reviewer-friendly release pack
Keep release work bounded and auditable

Primary workflows

Release readiness Changelog scope Artifact manifest Reviewer pack

Concrete workflow / priced call

Verify a tag pack before an operator cuts the tag

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

Request

“Can v1.2.0 be tagged from abc123?”

Execution

Tool call payload

{
  "tool": "releaseops_verify_tag_pack",
  "arguments": {
    "tag_name": "v1.2.0",
    "target_ref": "abc123",
    "existing_tags": [
      "v1.1.0"
    ],
    "worktree_clean": true
  }
}

Checks the supplied tag name, target ref, existing-tag list, and worktree state, then binds the verdict into a deterministic receipt hash.

Output

Exact deterministic output

{
  "contract": "releaseops.tag-pack.v1",
  "verdict": "PASS",
  "tag_name": "v1.2.0",
  "target_ref": "abc123",
  "worktree_clean": true,
  "blockers": [],
  "receipt_hash": "2a2f8eda6ba32eba5ec3d1bb6207a918a12caee1c21fa2200d6b7e07f92dd603"
}

Usage rating

At runtime

Recorded on the operation receipt

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