Skip to main content

Install proxymock CLI

Install proxymock to record traffic, mock dependencies, and replay tests. The same CLI supports local, CI/CD, Kubernetes, and cloud workflows. For a local workflow, start here and continue with the proxymock CLI quickstart.

Looking for speedctl install or platform resource commands? See Install speedctl CLI or choose a command-line tool.

Install with your coding agent (recommended)​

Let your coding agent (Claude Code, Cursor, Codex, Gemini CLI, Kiro, or any assistant that can read a URL and run commands) install proxymock for you. Paste this into the chat:

Install proxymock for me on this machine. First fetch the agent skill at
https://raw.githubusercontent.com/speedscale/skills/main/skills/install-speedscale/SKILL.md
and the references/ and scripts/ files it links to (same base URL), save them
under your skills directory, then follow the skill in local mode: proxymock and
its MCP server only, no Kubernetes operator.

The install-speedscale skill installs proxymock for your OS and walks you through proxymock init. Your recordings stay on your machine. It also connects the proxymock MCP server to your agent, so you can ask it to record, mock, and replay traffic. The agent stops for you at browser sign-in and asks before it changes anything outside your machine.

See Agent skills for the other skills.

Install proxymock manually​

Prefer to install it yourself? Pick your OS:

Install with Homebrew:

brew install speedscale/tap/proxymock

You can also manually run the install script (don't do this if your ran brew install):

sh -c "$(curl -Lfs https://downloads.speedscale.com/proxymock/install-proxymock)"

Optionally, install a specific version by passing it to the install script:

sh -c "$(curl -Lfs https://downloads.speedscale.com/proxymock/install-proxymock)" -s v2.3.456
Coding with AI Tools?

Install the proxymock MCP by running proxymock mcp install (--yes skips the per-client prompts). That command also drops the install-speedscale skill into Claude Code, so /install-speedscale can upgrade or repair everything later.

Kerberos cloud proxy​

If your outbound proxy requires Kerberos, configure Kerberos proxy authentication before running proxymock init or other cloud commands.

After installing​

Run proxymock --help to verify that the executable is on your PATH. If speedctl is already configured for your account, reuse its shared configuration. Otherwise initialize once before your first recording. Local use requires activation; your recorded traffic stays on your machine. Browser sign-in is the default path:

  • Run proxymock init and use the browser sign-in flow.
  • Use proxymock init --api-key <your key> only for CI or other headless environments.

For initialization details (enterprise accounts, CI, troubleshooting), see Initialize API Key.

Next: run the CLI quickstart​

Start with the proxymock CLI quickstart for your first complete record, mock, and replay loop. If you already have a cloud snapshot, pull and replay it locally instead.

Or follow the agent tutorial if you want an agent to perform each step. For language-specific application setup, use the examples below:

  • Java — Java demo app
  • Kotlin — Kotlin demo app
  • .NET — .NET demo app
  • Node.js — Node.js demo app
  • Go — Go demo app
  • Python — Python demo app
  • Ruby — Ruby demo app
  • PHP — PHP demo app
  • Rust — Rust demo app
  • C++ — C++ demo app