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.

Commands — Multimeter docs

npm (mmt-testlight), Homebrew, and GitHub Release binaries all expose the same testlight commands.Markdown (no JavaScript)# Commands npm (`mmt-testlight`), Homebrew, and GitHub Release binaries all expose the same `testlight` commands. - run <file> - Execute an API, test, suite, or load test file (.yaml/.yml/.json/.mmt) - Writes a JSON summary if `--out` is provided - Options: - `--example <name|#n>` — run a specific named example or numeric index (e.g., `--example happy-path` or `--example #1`) - `--tag <tag>` — only run tests/suites with this tag (repeatable, OR). See [suite tag filter example](../../../examples/intermediate/29_suite_tag_filter/README.md) - `--skip-tag <tag>` — skip tests/suites with this tag (repeatable, OR) - print-js <file> - Print the generated executable JS for a test file - Use this to inspect how a test will run - Options: - `--example <name|#n>` — print JS for a specific example - doc <file> - Generate documentation from a `type: doc` file (.mmt/.yaml/.yml) - Options: - `-o, --out <file>` — write output to file (default: `<docname>.html` in the current directory) - `--md` — generate Markdown instead of HTML - See [Doc](../../files/doc/index.md) for authoring `type: doc` files - version-info - Print the CLI and Node.js version - docs [topic] - Print bundled agent docs (same content as MCP `read_documentation`) - Topics: `overview` | `workflow` | `test` | `api` | `suite` | `env` | `doc` | `loadtest` | `constraints` | `all` | `offline` - `--pack min|full` (default `min`) - scaffold test --from <api.mmt> - Write a smoke test from an API file (same as MCP `scaffold_test`) - validate <file> - Validate a `.mmt` file (same as MCP `validate`) - suggest asserts --from <api.mmt> - Suggest assertions from an API or a response body (same as MCP `suggest_assertions`) - update - Refresh a **standalone / portal** binary from GitHub Releases (or a mirror) - Options: - `--check` — report whether an update is available without installing - `--to <version>` — install a specific version - `--channel <name>` — latest matching pre-release channel (`beta`, `rc`, `prerelease`) - `--force` — reinstall even if current is newest - `--base-url <url>` — portal mirror (`TESTLIGHT_RELEASE_BASE_URL`) - npm / Homebrew installs print the proper upgrade command instead of replacing files - See [Install](./install.md#update-standalone--portal-binaries) For AI agents · llms.txt · Home