Mostman CLI is now available on Docker Hub

We are excited to announce that Mostman CLI is now available on Docker Hub.

Docker hub page

This makes it much easier to use Mostman in local projects, team workflows, Docker-based automation, and CI/CD pipelines without needing a manual local installation.

Why this matters

With the new Docker image, teams can run Mostman CLI in a clean, portable, and consistent environment across machines and pipelines.

This is especially useful for:

• CI/CD jobs
• container-based automation
• teams that want the same CLI version everywhere
• users who prefer not to install the CLI directly on their machines

Pull the image

docker pull mohsenmcdt/mostman:latest

Better Docker and CI experience

Alongside the Docker image, Mostman CLI now supports environment-variable based defaults that make non-interactive usage much smoother.

Supported environment variables:

• MOSTMAN_TOKEN — Personal access token for non-interactive auth
• MOSTMAN_BASE_URL — Override Mostman server base URL
• MOSTMAN_WORKSPACE — Default workspace for commands supporting --workspace
• MOSTMAN_ENV — Default environment for run-request
• MOSTMAN_RUN_REMOTE — Default remote execution mode (true / false)
• MOSTMAN_TRACE — Enable trace output by default (true / false)
• OUTPUT_FORMAT - Default output format (text [default] /json/table/raw)

This means Docker and CI users can run commands without going through an interactive login flow first.

Example

docker run --rm \
  -e MOSTMAN_TOKEN=your_token_here \
  -e MOSTMAN_WORKSPACE=Dev \
  mohsenmcdt/mostman:latest collection list

And for running a request:

docker run --rm \
  -e MOSTMAN_TOKEN=your_token_here \
  -e MOSTMAN_WORKSPACE=Dev \
  -e MOSTMAN_ENV=staging \
  -e MOSTMAN_RUN_REMOTE=true \
  mohsenmcdt/mostman:latest collection run-request --name GetUsers

Backward compatible by design

This improvement does not replace the current CLI flow. Existing behavior continues to work as before.

Priority order is:

1. explicit CLI flags
2. environment variables
3. existing stored defaults or session
4. existing failure behavior

So local developer workflows remain unchanged, while Docker and CI usage become much smoother.

What’s next

This release is a step toward making Mostman easier to adopt in automation-heavy environments and modern developer workflows.

If you are already using Docker in your project or pipeline, you can now integrate Mostman CLI much more naturally.

Docker Hub

Mostman CLI Docker image: mohsenmcdt/mostman:latest

If you want to explore the image and start using it today, pull it from Docker Hub and try it in your workflow.