Deployment Simulated 3 MCP tools

Deployment Engine

Environment pipeline from dev → bench → staging → prod with health gates.

How you use it

Declare the env ladder and required checks. Agents call deploy_enforce for the next environment — never skip straight to prod.

Token savings

Prevents “deployed broken to prod → all-hands debug” token burn. Failures stay cheap on earlier envs.

Consistency

Environment order and gates are policy, not tribal knowledge. Same ladder for every agent session.

In action

Deployment
dev

Build + unit gates green.

bench
staging
prod

Interactive demo

Dev
Bench
Staging
Prod

GitHub Actions (simulated)

  • ● Checkout
  • ○ pnpm install
  • ○ pnpm build
  • ○ pnpm test
  • ○ Deploy bench
  • ○ Deploy staging
  • ○ Deploy prod

Health checks

Dev ○ waiting
Bench ○ waiting
Staging ○ waiting
Prod ○ waiting
Deployment movie Idle

Dev — build artifact

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

Diagram

Example usage

# .ags/deployment.yml (conceptual)
environments: [dev, bench, staging, prod]
gates:
  prod: [health, inventory]

# MCP: deploy_enforce
{ "target": "staging" }
Docs →
  • deploy_get
  • deploy_validate
  • deploy_enforce