Skip to main content
Glama

Download the video (MP4) ยท More demos

๐Ÿš€ Start with a request. Grow into a platform.

Multimeter is Git-native API testing in VS Code. Requests, tests, mocks, and docs are YAML .mmt files in your repo.

Start with a single HTTP request.

Grow into tests, suites, mocks, reports, documentation, and CI when you need them.

All in the same tool. No migration. No second product.

Related MCP server: jmeter-mcp-server

๐ŸŽฏ What you get

Simple by default

  • โœ… Git-native, file-based YAML

  • โœ… Lightweight โ€” no account, no cloud lock-in

  • โœ… Collaboration through pull requests, like code

  • โœ… The same files locally and in CI

A full testing platform when you need it

  • โœ… HTTP, WebSocket, GraphQL, and gRPC

  • โœ… Multi-step flows and test suites

  • โœ… Mock servers

  • โœ… Generated documentation

  • โœ… Reports

  • โœ… CI with testlight

AI in the same files

  • โœ… Generate tests from an API or a description (Cursor, Copilot, Claude via MCP)

  • โœ… Judge replies โ€” semantic similarity, or open-ended checks like how funny a response is

  • โœ… Bring your own model (Ollama or cloud)

See all features โ†’

โšก Start simple

Multimeter is a VS Code-native extension. All you need:

There you run a POST request as follows:

type: api
title: Simple POST
url: https://test.mmt.dev/echo
method: post
format: json
body:
  message: hello

That's enough.

  • No suites.

  • No mocks.

  • No workflows.

  • No complexity.

๐Ÿงช Need tests?

type: test
steps:
  - http: https://test.mmt.dev/echo
    method: get
    expect:
      status: 200
  • Still simple.

  • Still Git-native.

  • Still easy to review.

๐Ÿš€ Scale without switching tools

As your project grows, Multimeter grows with it.

Add:

  • Test suites

  • Mock servers

  • Documentation

  • Workflow execution

  • Structured reporting

  • CI artifacts

Only when you need them.

Everything stays in the same ecosystem.

See all examples โ†’

๐Ÿค– MCP, AI generation, and AI judges

Cursor, Copilot, and Claude write and run the same .mmt files you edit in VS Code. MCP (mmt-mcp) gives them scaffold_test, validate, format, and run โ€” generate tests from an API or a description, then keep them in Git.

Judge an API answer in the same test. Compare semantic similarity to an expected reply, or check something open-ended โ€” for example, how funny the response is. Bring your own model (Ollama or cloud). An alternative to a separate Promptfoo eval stack.

See MCP docs ยท Judge docs

๐Ÿ” Built for reliable CI

Multimeter validates test definitions before execution.

That means:

  • โœ… Earlier feedback

  • โœ… More deterministic execution

  • โœ… Fewer surprises in CI

  • โœ… Easier debugging

  • โœ… Reproducible results

GitHub Actions:

- uses: actions/checkout@v6
- uses: mshobeyri/testlight-action@v1
  with:
    file: tests/suite.mmt
    report: junit
    report-file: results/junit.xml

Or from a terminal using the Multimeter CLI called testlight.

npm install -g mmt-testlight
testlight run tests/suite.mmt

See the GitHub Action and Testlight install.

๐Ÿ“ฆ Everything stays in Git

Your code, tests, mocks, documentation, reports, and environment settings live in the same repository.

  • โœ… Version controlled

  • โœ… Code and tests evolve together

  • โœ… Reviewable through pull requests

  • โœ… Easy to move and share

  • โœ… No platform lock-in โ€” YAML in Git, plus Convert to Postman as an exit path

  • โœ… AI can update code and tests together

  • โœ… Environment variables never go missing

  • โœ… Historical test results stay with the project

๐Ÿง  Philosophy

Most API tools focus on requests.

Multimeter focuses on behavior.

Instead of asking:

"Did this request return the expected response?"

Multimeter helps you answer:

"Does this system still behave correctly?"


License

Multimeter is licensed under the Apache License 2.0.

Demos ยท Documentation ยท Website ยท GitHub

Available Tools

9 tools
api_cardCompact API cardA
Read-only

Return a small API summary (method, url, inputs, outputs, suggested paths) without dumping the full file. Prefer this over reading the whole .mmt or OpenAPI when generating or planning a test. Next step for a new test: scaffold_test. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: apiPath (required), workspaceRoot (required).

discover_apiDiscover workspace APIsA
Read-only

Call when listing APIs or inspecting one API before scaffolding a test. For a single API, prefer api_card. For new tests, prefer scaffold_test once apiPath is known. selectedApi omits full file content unless includeContent is true. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: workspaceRoot (required), apiPath, includeContent.

formatFormat .mmt fileB
Read-only

Format a Multimeter file using canonical field ordering and style rules. Call after validate passes when normalizing generated or edited YAML. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: file (required), workspaceRoot.

list_examplesList Multimeter examplesA
Read-only

Call when you need example .mmt structure before creating or modifying a file. Prefer this over searching the repo or guessing YAML layout. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: type, category, maxItems, includeContent.

read_documentationRead Multimeter docsA
Read-only

Call when you need Multimeter YAML syntax rules. Defaults to pack "min" (small). Use pack "full" only for rare/advanced syntax. For new tests from an API, prefer scaffold_test over loading docs. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: pack, topic.

runRun .mmt fileA

Execute a Multimeter test or API file and return structured pass/fail output, logs, and errors. ONLY supported way to run .mmt files from Copilot โ€” call this directly when the user asks to run or execute. Do NOT use testlight CLI, npx, npm install, shell scripts, or node dist/mcp/server.js.

Inputs: file (required), env, quiet, inputs, +1 more.

scaffold_testScaffold test from APIA
Read-only

REQUIRED first step when generating a new Multimeter test from an existing API .mmt. Returns valid smoke (or example) test YAML, suggested path, import alias, and a compact apiCard. Write the yaml, apply only minimal edits, then validate. Do not invent a blank test from scratch. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: apiPath (required), workspaceRoot (required), alias, outPath, +1 more.

suggest_assertionsSuggest assert/expect patchesA
Read-only

Suggest compact expect/assert YAML patches from API outputs and/or a JSON response body. Use after a run or when tightening a scaffolded smoke test โ€” patch only, do not rewrite the file. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: body, style, status, stepId, +4 more.

validateValidate .mmt fileA
Read-only

REQUIRED after every create or modify operation on a .mmt file. Call immediately after editing a file and before telling the user the task is done. Returns structured errors and fix suggestions. Do not use testlight, npx, npm, shell, or node dist/mcp/server.js.

Inputs: file (required), expectedType, workspaceRoot.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools map to distinct workflow stages: learning syntax, seeing examples, discovering APIs, scaffolding, validating, formatting, and running. discover_api and api_card overlap for single-API inspection, but the descriptions make the preferred choice clear.

    Naming Consistency4/5

    Tool names mostly follow an imperative verb_noun pattern such as read_documentation, list_examples, discover_api, scaffold_test, validate, and run. api_card breaks the pattern as a noun-only name, but the inconsistency is minor and not confusing.

    Tool Count5/5

    Nine tools is well-scoped for this server's purpose of discovering, generating, validating, formatting, and running Multimeter tests. Each tool serves a clear role in the workflow without redundancy or bloat.

    Completeness4/5

    The toolset covers the core lifecycle from API discovery and test scaffolding to assertion suggestions, validation, formatting, and execution. A few peripheral capabilities like listing or deleting existing tests are absent, but agents can complete the primary authoring workflow without dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      CLI-first API testing tool with MCP server. Tests are .tarn.yaml; failures come back as structured JSON for AI agents to branch on. Tools: tarn_run, tarn_validate, tarn_fix_plan, tarn_inspect, tarn_rerun_failed.
      14
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables running YAML-defined test suites against MCP servers and agent workflows, with live or simulated execution, assertions, and regression reporting.
      72 npm
      MIT