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.

Format — Multimeter docs

format controls how Multimeter encodes the request body and decodes the response body.Markdown (no JavaScript)# Format `format` controls how Multimeter encodes the request body and decodes the response body. - Values: `none` | `json` | `xml` | `xmle` | `text` | `html` | `urlencoded` | `binary` | `multipart` | `auto` - Optional — both sides default to `auto` when omitted - Explicit `format: json` pins the request to json; response stays `auto` - Affects default `Content-Type` and body handling - The request format picker omits `html` (use `text` for HTML request bodies). `format: html` in YAML still works; response `html` remains available for pretty/preview Use a single value to pin the **request** format; response stays `auto` unless you set it explicitly: ```yaml format: json ``` Split request and response when the response format should differ from `auto`: ```yaml format: request: json response: xml ``` **Request `auto`** (default when omitted) uses the request `Content-Type` header; when that header is missing, Multimeter assumes `json`. **Response `auto`** (default when omitted) uses the response `Content-Type` header; when that header is missing, Multimeter falls back to the resolved request format, then body sniffing — similar to Postman’s **Auto** response view. | Format | Typical use | |---|---| | `none` | No request body (Postman **none**) | | `json` | JSON APIs (default) | | `xml` | XML with self-closing empty tags (`<meta/>`) | | `xmle` | Expanded XML with explicit closing tags (`<meta></meta>`) | | `text` | Raw text body | | `html` | Response HTML pretty/preview (`text/html`). Prefer `text` when authoring request bodies in the tester | | `urlencoded` | Form fields as `application/x-www-form-urlencoded` | | `binary` | File path relative to the `.mmt` file | | `multipart` | Form parts (`name` + text `value` or relative `file` path); Postman **form-data** (`multipart/form-data`) | The `body` field shape depends on `format`. See [Request body](./body.md) and [HTTP bodies](../protocols/http-bodies.md). Not used with GraphQL (`format` is always JSON) or gRPC (the `grpc` block replaces `body` and `format`). See also: [Body overview](./index.md) · [Request fields](../index.md#request) · [HTTP](../protocols/http.md) For AI agents · llms.txt · Home