Restorm Documentation

Restorm is a desktop API testing environment: a client that speaks fifteen protocols, a mock server, a visual scenario editor and an automation engine you can run in continuous integration. This documentation covers the whole product.

Where to start

• New to Restorm? Read What is Restorm?, then Installation and the Quick start.
• Coming from Postman, Bruno or Insomnia? Start with Migrating from Postman — your collections import as they are.
• Looking for a specific protocol? The protocol catalogue has one page per supported protocol.
• Automating things? See scenarios and headless execution in CI.

The product’s main building blocks

Block	What you do there
Concepts	.restorm projects, requests, folders, environments, variables, authentication
Protocols	HTTP, GraphQL, gRPC, SOAP, WebSocket, Socket.IO, MQTT, SSE, STOMP, OData, JSON-RPC, tRPC, Redis, AMQP, Kafka
Import & export	24 import formats (OpenAPI, Postman, Bruno, HAR, cURL…) and code snippet export
Scenarios	Chain calls, branch, loop, assert, run in CI
Server mode	Host mock servers built from your own requests
Tools	Mini browser, firewall, console, built-in git, AI-driven control over MCP
Reference	Handlebars helpers, shortcuts, settings, CLI, MCP tools

What sets Restorm apart

• Everything is local. Projects are files on your own disk, mock servers run on your machine, and no round trip through a third-party service is ever required.
• A single tool for every transport. The same project tree holds your REST calls, your MQTT subscriptions, your Kafka consumers and your streaming gRPC calls.
• Version-control friendly. The file format is serialised deterministically to keep git diff readable, and Restorm ships a git client with domain-aware conflict resolution.
• Drivable by an AI. Restorm exposes an MCP server: an agent can read your project, run requests and drive the interface.