Cli Anything Wiremock

by hkuds34f519533bc1No licenseListed Oct 8, 2026Updated Oct 8, 2026

Python CLI harness for WireMock HTTP mock server administration

Instructions onlySoftware Development
AI-generated overview

CLI harness for administering a WireMock HTTP mock server via its Admin REST API.

What it does
This skill documents a command-line interface that wraps the WireMock Admin REST API. It covers command groups for managing stub mappings, inspecting served requests, controlling stateful scenarios, recording traffic from a real backend, and reading global server settings, plus top-level status, reset and shutdown commands. It produces JSON output for agent use and supports connection configuration through environment variables.
When to use it
Use it when an agent or developer needs to set up, inspect or tear down HTTP stubs on a running WireMock server. It fits integration-test verification workflows where requests must be counted or matched against stubs, and traffic from a real backend must be recorded.
Requirements
Requires a reachable WireMock server and its Admin REST API; connection is configured with the WIREMOCK_HOST and WIREMOCK_PORT environment variables. The skill ships no scripts and is instructions only.

Overview

cli-anything-wiremock is a command-line interface that wraps the WireMock Admin REST API (/__admin/). It allows agents and developers to manage HTTP stub mappings, inspect served requests, control stateful scenarios, and record real backend traffic — all from the terminal or from agent tool calls.

WireMock is commonly used in integration testing environments to replace real HTTP backends with controllable mock responses.

Command Groups

stub — Manage HTTP stub mappings

CommandDescription
stub listList all registered stubs
stub get <id>Get details of a specific stub by UUID
stub create <json>Create a stub from a JSON string
stub quick M URL SQuickly create a stub: METHOD URL STATUS_CODE
stub delete <id>Delete a stub by UUID
stub resetReset all stubs to the defaults on disk
stub savePersist in-memory stubs to disk
stub import <file>Import stubs from a JSON file

request — Inspect served requests

CommandDescription
request listList recent served requests
request find <pattern>Find requests matching a JSON pattern
request count <pattern>Count requests matching a JSON pattern
request unmatchedList requests that matched no stub (404s)
request resetClear the request journal

scenario — Stateful scenario management

CommandDescription
scenario listList all scenarios and current states
scenario set N SSet scenario NAME to STATE
scenario resetReset all scenarios to their initial state

record — Record traffic from a real backend

CommandDescription
record start <url>Start proxying + recording to TARGET_URL
record stopStop recording, return captured stubs
record statusCheck if currently recording
record snapshotSnapshot in-memory requests as stubs

settings — Global server settings

CommandDescription
settings getGet current global WireMock settings
settings versionShow WireMock server version

Top-level commands

CommandDescription
statusCheck if WireMock is running
resetFull reset: stubs + requests + scenarios
shutdownGracefully shut down the WireMock server

Key Examples

bash
# Check connectivitycli-anything-wiremock status
# Create a stub using quick formcli-anything-wiremock stub quick GET /api/users 200 --body '[{"id":1}]'
# Create a stub using full JSONcli-anything-wiremock stub create '{  "request": {"method": "POST", "url": "/api/orders"},  "response": {"status": 201, "body": "{\"id\":99}"}}'
# Verify a POST was made exactly oncecli-anything-wiremock --json request count '{"method":"POST","url":"/api/orders"}'# → {"count": 1}
# Scenario: advance statecli-anything-wiremock scenario set "cart-flow" "item-added"
# Record a real backendcli-anything-wiremock record start https://api.example.com# ... make requests ...cli-anything-wiremock record stop

Agent Guidance

Always use --json in agent contexts

Use --json for all invocations in scripts or agent tool calls. JSON output varies by command type (these are distinct response types, not an envelope wrapping all responses):

bash
# Data commands return raw WireMock API JSON directly:cli-anything-wiremock --json stub quick GET /api/hello 200 --body '{"hello":"world"}'# → {"id": "abc-123", "request": {...}, "response": {...}, ...}
cli-anything-wiremock --json stub list# → {"mappings": [...], "total": N}
# Void commands (delete, reset, save) return:# → {"status": "ok"}
# Errors return:# → {"status": "error", "message": "Connection refused"}

Connection via environment

Set connection params via environment variables before calling any command:

bash
export WIREMOCK_HOST=localhostexport WIREMOCK_PORT=8080

Workflow pattern for test verification

  1. Set up stubs before running the system under test:
    bash
    cli-anything-wiremock --json stub quick POST /api/payment 200 --body '{"success":true}'
  2. Run the system under test.
  3. Verify interactions:
    bash
    cli-anything-wiremock --json request count '{"method":"POST","url":"/api/payment"}'
  4. Clean up:
    bash
    cli-anything-wiremock reset

Error handling

Non-zero exit code on all errors. In --json mode, errors return {"status": "error", "message": "..."}. Success returns the raw WireMock API response.

Source and attribution

Source:hkuds/cli-anythinginskills/cli-anything-wiremockat commit34f5195

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal