The pairing that matters is import plus execute: a cURL line, a Postman export or an OpenAPI spec becomes a real collection, and the request then actually runs with the environment resolved — workspace, sub-environment, folder chain, per-call overrides, in that order — so what comes back is the response rather than a rendered command. And because it reads and writes the installed Insomnia app's own database, work done here shows up in the GUI and work done in the GUI shows up here.
An API collection manager that stores collections in Insomnia's format and can also read and write the installed Insomnia app's own database directly. It creates and runs requests, resolves environment variables in layers at execution time, and imports from cURL, Postman and OpenAPI.
- Collections and folders created, listed, inspected with statistics, and exported as Insomnia V4 JSON
- Requests created, updated, deleted and listed, with method, URL, headers, parameters, body and authentication
- A request executed and its response returned, with a timeout defaulting to 30000 ms and a cap on how much of the body comes back
- Execution history per request, up to 20 entries
- Environment variables set and read, and resolved in layers when a request runs — workspace, sub-environment, the folder chain, then per-call overrides
- Imports from a cURL command, a Postman v2.1 collection, an OpenAPI 3.x or Swagger 2.x spec, or an Insomnia V4 export
- Code snippets generated for a request in c, clojure, csharp, go, http, java, javascript, kotlin, node, objc, ocaml, php, powershell, python, ruby, shell or swift, with a client library selectable
- Direct access to the installed Insomnia app on macOS, Linux and Windows: projects and workspaces listed, a request read, one workspace imported or all of them, a collection pushed back, and a request executed in place with no syncing
- Keyword search across every collection, folder and request, plus global statistics
Node.js 18 or newer, launched with npx -y mcp-insomnia over stdio, installed globally, or built from source. No account and no key — collections live in the server's own storage. The tools that reach the installed Insomnia application read its local NeDB database directly, so Insomnia has to be on the machine for those to do anything.
One command — npx -y mcp-insomnia