Multimeter is a Git-native REST client and API testing tool for VS Code. Requests, tests, mocks, and docs are YAML .mmt files in Git — the same files in the visual editor and in CI via testlight. Apache 2.0. No account.

How do I use Multimeter with Cursor, Copilot, or Claude?

Install the VS Code/Cursor extension or add MCP with npx -y mmt-mcp. Agents should call scaffold_test, validate, format, and run instead of guessing .mmt syntax.

Yes. Apache License 2.0. No account required.

CLI — Multimeter docs

Use -F / --env-file and -P / --preset to load variables from an env file, then override with -e:Markdown (no JavaScript)# Environment variables on the CLI Use `-F` / `--env-file` and `-P` / `--preset` to load variables from an env file, then override with `-e`: ```sh testlight run tests/login.mmt -F env.mmt -P runner.dev ``` Apply multiple preset groups (same as the environment panel): ```sh testlight run tests/login.mmt -F env.mmt -P runner.dev -P custom.prod ``` Override values explicitly (wins over preset): ```sh testlight run tests/login.mmt -F env.mmt -P runner.dev \ -e api_url=http://localhost:8080 -e user=bob ``` Without an env file, pass variables directly: ```sh testlight run tests/login.mmt -e api_url=http://localhost:8080 -e user=alice -e pass='00123' ``` **Typing rules:** unquoted numbers and booleans are coerced (`true`, `42`); quoted values stay strings (`'00123'`). From a test or suite editor, **More → Run in testlight** builds `testlight run <file> …` with the current workspace environment (matching presets as `-F` + `-P group.option`, extras as `-e`), copies it, and runs it in a terminal. See [Testlight — Options](../../features/testlight/options.md) · [Testlight — Environment priority](../../features/testlight/environment-priority.md) · [Testlight](../../features/testlight/index.md) For AI agents · llms.txt · Home