Developer tools

Developer and operator tools for Shopify checkout monitoring

By Gary Gillespie · Last updated 2 October 2026

Most checkout monitoring lives behind a dashboard. If you are an engineer, an ops person or an agency, you usually want it in your terminal, your CI pipeline, or an AI assistant instead. These guides cover the ways to run Revenue Shield checkout monitoring as code.

The rs CLI CLI

Onboard a store, list tests, trigger runs and pull video evidence from your terminal or CI.

The MCP server MCP

Monitor with Claude AI

Ask an AI assistant to check a store, run a test and explain a failure, using the MCP tools.

For agencies Agencies

Script checkout monitoring across a portfolio of client stores from one CLI or AI assistant.

Automated checkout testing Testing

Scheduled, scriptable real-purchase tests on desktop and mobile, with video and trace evidence.

What these tools wrap

Revenue Shield's core job is a synthetic checkout test: it adds a real product to cart and walks through to the payment step on desktop and mobile, on a schedule, and records a video and a Playwright trace each time. A generic uptime monitor returns HTTP 200 while that path is broken; this proves a customer can actually buy.

The developer tools do not re-implement any of that. They are thin wrappers over the same recorder-api the merchant dashboard and agency portal already call. The command line tool (rs) and the MCP server (rs-mcp) expose the same operations: onboard a store by URL, list its tests, trigger a run, read run history, and fetch the signed video and trace for a run.

Two surfaces, one engine

Surface	Best for	How you use it
`rs` CLI	Terminals, scripts, CI pipelines	One command per operation, with a `--json` mode for piping into jq or a build step
`rs-mcp` MCP server	Driving monitoring from Claude in plain language	Register the local server as a custom connector, then ask the assistant to list tests, run one, or pull the evidence for a failure

Both split their commands into a safe MONITORING tier (read, trigger a run, onboard a store) and an internal OPS tier (pause, regenerate, edit a spec). The MONITORING tier is the slice designed to be handed to an agency or an AI agent later.

Frequently asked questions

Is there a Shopify checkout monitoring API I can call?

Yes, indirectly. The rs CLI and MCP server are thin clients over Revenue Shield's existing API, so every command maps to an endpoint that is already live. There is no separate public, versioned API contract yet; the supported way to script monitoring today is through these tools.

Do I need to be a developer to use Revenue Shield?

No. The dashboard covers everything most merchants need. These tools are for people who specifically want to run monitoring from a terminal, from CI, or from an AI assistant.

See it on your own store — free

Run a free checkout health scan on any live Shopify store. No install, no card. Results in about 8 minutes, with step-by-step video proof.

Scan my store free or install on Shopify →

Rated 5/5 by merchants on the Shopify App Store