Release Simulated 4 MCP tools

Release Engine

Inspect release artifacts, tags, and generated notes.

How you use it

Before tagging: release_plan → produce artifacts/notes → release_enforce. Pair with versioning and artifact engines.

Token savings

Avoids half-shipped releases that bounce between “forgot changelog” and “wrong tag” repair sessions.

Consistency

Every release matches the declared artifact + notes + tag contract.

In action

Release
Artifacts

release_get lists required outputs.

Validate
Gap
Enforce

Interactive demo

Release pipeline Idle

Artifacts

  • @ags/governance-engine.tgz 142 KB
  • tower-mcp-bundle.zip 890 KB
  • checksums.sha256 1.2 KB

Generated notes

Release notes pending…

Simulated behavior only — does not execute proprietary AGS engine code.

Diagram

Example usage

# .ags/release.yml
artifacts:
  - dist/**
  - CHANGELOG.md
notesRequired: true

# MCP: release_enforce
{}
Docs →
  • release_get
  • release_validate
  • release_enforce
  • release_plan