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.

Reference — Multimeter docs

- type: test - title: string - tags: string[] - description: string (supports Markdown; use |- for multiline). Optional <<i:name>> / <<o:name>> annotations…Markdown (no JavaScript)# Reference (types) - `type:` `test` - `title:` string - `tags:` string[] - `description:` string (supports Markdown; use `|-` for multiline). Optional `<<i:name>>` / `<<o:name>>` annotations (and `[...]` allowed values / ranges) — see [Input and output documentation](../input-output-docs.md) - `import:` record<string, string> — see [import](./import.md) (`.mmt`, `.http`/`.https`, `.bru`, CSV / JSON / YAML data files; `.js`/`.cjs`/`.mjs`: [js helper modules](./steps/js.md#js-helper-modules)) - `inputs:` record<string, string | number | boolean | null> - `outputs:` record<string, string | number | boolean | null> - `cache:` number \| string (optional; duration like `5m`, epoch number, or date/time text containing `:`) - `steps:` array of step (`alias:` `flow`) - `stages:` array of { id, title?, steps, condition?, after? } - step types: `call`, `http`, `check`, `assert`, `if`, `for`, `repeat`, `delay`, `js`, `print`, `set`, `var`, `const`, `let`, `setenv`, `run` Notes: - `flow` is accepted as a backward-compatible alias for `steps`. - The YAML editor provides autocomplete for `call` step names, check/assert [operators](./operators.md), and input references. `report:` on checks/expects accepts `all` | `fails` | `none` — see [Reports — Report levels](./reports.md#report-levels-all-fails-none). - YAML comments (`#`) are preserved when you format the file (Format Document). Prefer `description` / step `title` for structured docs that survive UI edits. --- For AI agents · llms.txt · Home