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.

History — Multimeter docs

See and inspect recent requests and responses made from the Multimeter UI and CLI.Markdown (no JavaScript)# History See and inspect recent requests and responses made from the Multimeter UI and CLI. Use the History panel to review what was sent, what came back, and how long it took—handy for debugging, demos, and sharing context with teammates. ![History panel listing recent requests with method, URL, status, duration, and timestamp](../screenshots/history.png) ## What you can use it for - Troubleshoot failing or flaky calls (status, duration, headers, body) - Compare multiple runs while iterating on an API - Keep a quick, local trail of interactions during a session - Share a snapshot (copy details) for support or review ## How it works - Every request you send from the API editor (and supported actions) is recorded - Entries show method, URL, status code, duration, and timestamp. Network failures (invalid URL, TLS/cert errors, unreachable host) store the error text instead of only `-1` - Select an entry to see `details:` - Request: method, URL, headers, cookies, and body - Response: status, headers, cookies, and body ## Panel controls - Filter/search (when available): narrow the list by method, status, or text - Delete: remove a single history entry - Clear History: remove all entries ## Tips - Use History alongside the Environment presets to confirm you’re hitting the right base URL - Sort by timestamp or status (when available) to spot regressions quickly - Copy request/response snippets to share with teammates or to build test cases ## Notes and limits - History is local to your workspace; it isn’t synced or persisted across machines - Very large bodies may be truncated in the panel for performance - Sensitive data can appear in history—use Clear History when needed --- ## See also - [Panels](./index.md) — all sidebar and bottom panels - [API](../files/api/index.md) — requests made from the API editor appear in history - [Test](../files/test/index.md) — test runs generate requests visible in history - [Mock Server](../files/server/index.md) — mock server file and panel requests are also recorded - [Mock server panel](../files/server/panel.md) — sidebar panel request history - [Environment](../files/env/index.md) — confirm you’re hitting the right base URL - [Browse examples](/docs/examples) — sample Multimeter projects For AI agents · llms.txt · Home