
Cli Anything Wiremock
- 347 installs
- 46.6k repo stars
- Updated August 3, 2026
- hkuds/cli-anything
cli-anything-wiremock is a Python CLI harness that manages WireMock stub mappings and scenarios via the WireMock Admin REST API for developers who need stable fake HTTP dependencies in tests.
About
cli-anything-wiremock is a Python command-line interface that wraps the WireMock Admin REST API at `__/__admin__/` for developers who need controllable fake HTTP backends. The CLI helps manage stub mappings, inspect served requests, control stateful scenarios, and record real backend traffic so test suites and local development can run against predictable responses. Developers reach for cli-anything-wiremock when frontend and backend teams need a stable contract, when CI integration tests must avoid flaky upstream dependencies, or when reproducing edge-case HTTP behaviors reliably. cli-anything-wiremock is also suitable for agent tool calls that orchestrate mocks as part of automated test pipelines.
- WireMock stub lifecycle via cli-anything
- Agent-controlled HTTP dependency mocks
- Supports contract and integration testing
- Stable fake APIs for parallel dev
- Backend decoupling during build
Cli Anything Wiremock by the numbers
- 347 all-time installs (skills.sh)
- +12 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #1,163 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hkuds/cli-anything --skill cli-anything-wiremockAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 347 |
|---|---|
| repo stars | ★ 46.6k |
| Last updated | August 3, 2026 |
| Repository | hkuds/cli-anything ↗ |
How do I manage WireMock stubs from CLI?
Let agents start WireMock stubs, load mappings, and simulate HTTP dependencies so backend and frontend teams can develop and test against stable fake APIs.
Who is it for?
Developers running integration tests that depend on stable, controllable HTTP mock responses.
Skip if: Developers who need unit test assertion libraries rather than HTTP dependency simulation.
When should I use this skill?
Trigger cli-anything-wiremock when a workflow needs to start/update WireMock stubs or inspect `__admin` requests during tests.
What you get
Configured WireMock stub mappings, scenario state, recorded traffic, and inspected request logs.
- WireMock mappings
- Request inspection output
- Recorded stub data
By the numbers
- The CLI metadata declares version 0.1.0.
- The tool targets the WireMock Admin REST API path `/_ _admin_/`.
Files
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
| Command | Description |
|---|---|
stub list | List 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 S | Quickly create a stub: METHOD URL STATUS_CODE |
stub delete <id> | Delete a stub by UUID |
stub reset | Reset all stubs to the defaults on disk |
stub save | Persist in-memory stubs to disk |
stub import <file> | Import stubs from a JSON file |
request — Inspect served requests
| Command | Description |
|---|---|
request list | List recent served requests |
request find <pattern> | Find requests matching a JSON pattern |
request count <pattern> | Count requests matching a JSON pattern |
request unmatched | List requests that matched no stub (404s) |
request reset | Clear the request journal |
scenario — Stateful scenario management
| Command | Description |
|---|---|
scenario list | List all scenarios and current states |
scenario set N S | Set scenario NAME to STATE |
scenario reset | Reset all scenarios to their initial state |
record — Record traffic from a real backend
| Command | Description |
|---|---|
record start <url> | Start proxying + recording to TARGET_URL |
record stop | Stop recording, return captured stubs |
record status | Check if currently recording |
record snapshot | Snapshot in-memory requests as stubs |
settings — Global server settings
| Command | Description |
|---|---|
settings get | Get current global WireMock settings |
settings version | Show WireMock server version |
Top-level commands
| Command | Description |
|---|---|
status | Check if WireMock is running |
reset | Full reset: stubs + requests + scenarios |
shutdown | Gracefully shut down the WireMock server |
Key Examples
# Check connectivity
cli-anything-wiremock status
# Create a stub using quick form
cli-anything-wiremock stub quick GET /api/users 200 --body '[{"id":1}]'
# Create a stub using full JSON
cli-anything-wiremock stub create '{
"request": {"method": "POST", "url": "/api/orders"},
"response": {"status": 201, "body": "{\"id\":99}"}
}'
# Verify a POST was made exactly once
cli-anything-wiremock --json request count '{"method":"POST","url":"/api/orders"}'
# → {"count": 1}
# Scenario: advance state
cli-anything-wiremock scenario set "cart-flow" "item-added"
# Record a real backend
cli-anything-wiremock record start https://api.example.com
# ... make requests ...
cli-anything-wiremock record stopAgent 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):
# 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:
export WIREMOCK_HOST=localhost
export WIREMOCK_PORT=8080Workflow pattern for test verification
1. Set up stubs before running the system under test:
cli-anything-wiremock --json stub quick POST /api/payment 200 --body '{"success":true}'2. Run the system under test. 3. Verify interactions:
cli-anything-wiremock --json request count '{"method":"POST","url":"/api/payment"}'4. Clean up:
cli-anything-wiremock resetError handling
Non-zero exit code on all errors. In --json mode, errors return {"status": "error", "message": "..."}. Success returns the raw WireMock API response.
Related skills
How it compares
Pick this when you need scripted WireMock administration; pick direct WireMock files when you only need static mappings with no runtime control.
FAQ
What API does cli-anything-wiremock talk to?
cli-anything-wiremock talks to the WireMock Admin REST API at `/_ _admin_/` as described in its overview. cli-anything-wiremock uses that admin surface to manage stub mappings, inspect served requests, control scenarios, and optionally record traffic for replay.
When is cli-anything-wiremock better than hand-editing JSON mappings?
cli-anything-wiremock is better when the workflow needs repeatable automation, such as loading mappings in CI, resetting scenarios between tests, or inspecting request journals after failures. cli-anything-wiremock provides terminal-friendly commands that integrate cleanly into s