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.

Tokens — Multimeter docs

Echo request data and inject dynamic values in type: server responses. See Endpoints for the overall file shape.Markdown (no JavaScript)# Server tokens Echo request data and inject dynamic values in `type: server` responses. See [Endpoints](./endpoints.md) for the overall file shape. ### Echoing request data Use `${namespace.field}` placeholders in response `body` values (and inside strings): | Namespace | Syntax | Source | |-----------|--------|--------| | URL | `${url.id}` | Path parameters from route patterns like `/users/:id` | | URL | `${url.path}` | Full request path (without query string) | | Body | `${body.name}` | Parsed request body (JSON or XML → object) | | Header | `${header.authorization}` | Incoming request headers (case-insensitive) | | Query | `${query.page}` | Query string parameters | ```yaml body: id: "${url.id}" received_name: "${body.name}" client_key: "${header.x-api-key}" page: "${query.page}" message: "Created user ${body.name} with id ${url.id}" ``` Request bodies are parsed automatically from JSON or XML. Nested fields use dot notation: `${body.user.email}`. In the YAML editor, type `${` to get autocomplete for `url.`, `body.`, `header.`, and `query.` — including path parameter names from your endpoint paths. ### Environment, random, and current tokens Mock responses use the same dynamic tokens as APIs and tests. Values are resolved when the mock handles a request, using the active environment (VS Code Environment panel, suite `environment`, or CLI `--env-file` / `-e`): | Token | Example | Description | |-------|---------|-------------| | `e:var` / `<<e:var>>` | `email: e:admin_email` | Environment variable | | `r:name` / `<<r:name>>` | `id: r:uuid` | Random value (new per request) — [full list](../../features/dynamic-values/random.md) | | `c:name` / `<<c:name>>` | `created: c:date` | Current date/time — [full list](../../features/dynamic-values/current.md) | `e:` tokens also work in response headers, `match` rules, path patterns, `port`, and `protocol`: ```yaml type: server protocol: e:mock_protocol port: e:mock_port endpoints: - method: get path: <<e:base_path>>/users match: headers: x-api-key: e:api_key status: 200 headers: X-Mock-Env: e:env_name body: email: e:admin_email greeting: "Hello from <<e:env_name>>" ``` Set `mock_port` / `mock_protocol` (and other vars) in the Environment panel, a suite `environment`, or via CLI `--env-file` / `-e`. While typing an incomplete token such as `protocol: e:`, YAML may temporarily parse it as a nested map — Multimeter treats that as a validation error instead of crashing the editor. See also: [Endpoints](./endpoints.md) · [Dynamic values](../../features/dynamic-values/index.md) · [Environment](../env/index.md) For AI agents · llms.txt · Home