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.

Edit Test — Multimeter docs

Open a test file in VS Code and click in the runner top bar to switch from the test runner to edit mode. Use the back control on the edit header to return…Markdown (no JavaScript)# Edit Test Open a test file in VS Code and click {{btn:edit:Edit Test}} in the runner top bar to switch from the **test runner** to **edit mode**. Use the back control on the edit header to return to the runner. Edits in edit mode write directly to the YAML. Runner input edits are temporary until you **Save to YAML** or **Discard**. The separate {{btn:type-hierarchy-sub:Flow chart}} control opens a read-only flowchart view — it is not part of edit mode. ## Tabs | Tab | What you edit | |---|---| | {{btn:search:Overview}} | `title`, `description`, `tags`, `import`, `inputs`, `outputs`, `cache` | | {{btn:list-tree:Flow}} | Visual step editor for `steps:` or `stages:` | | {{btn:code:Code}} | JavaScript compiled from the YAML test — generated output, not the source file | ### Overview | Field | Notes | |---|---| | `title` | Maps to `title:` | | `tags` | Searchable tag chips; maps to `tags:` | | `description` | Markdown editor; maps to `description:`. Use `<<i:name>>` / `<<o:name>>` annotations (and `[...]` allowed values) — see [Input and output documentation](../input-output-docs.md) | | `import` | Alias → path pairs with file picker (`.mmt`, CSV/JSON/YAML data, JS helper modules). Missing paths are highlighted | | `inputs` | Default input values for `i:` tokens | | `outputs` | Output variable declarations | | `cache` | Optional cache duration (`5m`), epoch number, or date/time string — see [cache](./cache.md) | ### Flow The Flow tab is a visual editor for test steps. Each step type appears as a block you can add, reorder, and configure inline. Stages (parallel groups separated by `then`) are supported when the test uses `stages:` instead of a flat `steps:` list. Use **Add item** to insert new steps (call, http, assert, delay, control flow, and more). The Flow view corresponds directly to the step types documented under [Steps](./steps/index.md). ![Flow view — call, delay, and const step blocks](../../screenshots/test-steps-flow.png) ### Code The Code tab shows the JavaScript Multimeter generates from your YAML. It is read-only — edit the YAML or use the Flow tab to change behavior. --- See also: [Test overview](./index.md) · [Quick start](./quick-start.md) · [Steps](./steps/index.md) · [Reference](./reference.md) For AI agents · llms.txt · Home