A Postman alternative inside VS Code, without signing in

Postman is a full API platform: workspaces in the cloud, mock servers, monitors, scripting, documentation. If what you actually do most days is send a request to the API you are building and check the response, you can do that inside your editor with Plainwire: a free, open-source GUI API client for VS Code, Cursor, Windsurf and VSCodium that needs no account and stores requests as plain .http files in your repository.

Plainwire is an independent open-source project. It is not affiliated with or endorsed by Postman, Thunder Client or REST Client. Postman is a trademark of its owner.

What Postman asks for today

As read on 20 November 2026:

None of that is a problem if you use Postman’s platform features. It is friction if you just want requests that live next to the code, get reviewed in pull requests and run in CI.

Comparison

Facts about Postman come from the pages linked above. “Not verified” means we could not confirm it either way.

PlainwirePostman (VS Code extension, Free plan)
PriceFree, MIT open sourceFree for 1 user; Team $19/user/month (billed annually)
Account to send requestsNeverSign-in required for the extension
Where requests live.http files in your repositoryPostman workspaces
Team sharingThrough git, free, any team sizePostman workspaces (Free plan: 1 user)
GUI request editor and response viewerYesYes
Environments and variablesYes (http-client.env.json)Yes
Tests# @assert lines and JavaScript client.test; imported pm.test scripts runJavaScript test scripts
Pre-request / test scripts in JavaScriptYes, since 0.13: JetBrains < {% %} / > {% %} scripts and a Postman-compatible pm API, without pm.sendRequest (guide)Yes
Collection runner and CLI for CIRun all + free CLI and GitHub ActionCollection Runner; Postman CLI
GraphQLYes, Query + Variables editor (guide)Yes
WebSocketYes, since 0.12 (guide)Yes
gRPCNot yetYes
Mock servers, monitors, API docsNoYes
Copy request as codeYes: cURL, JavaScript, Node.js, Python, Go, HTTPie, PowerShell, wget, C#, PHP, JavaYes
Works offlineYes, nothing but your own requests leaves your machineNot verified
TelemetryNoneNot verified

Move a Postman collection in two minutes

  1. Export the collection from Postman (collection menu → Export → Collection v2.1) and each environment you need.
  2. Install Plainwire from the latest release (install steps).
  3. Run Plainwire: Import from Postman… and pick the exported files. Each folder becomes a .http file; environments go to http-client.env.json; collection variables become @name = value lines; common tests become # @assert lines; other test scripts and pre-request scripts are kept as > {% %} / < {% %} blocks that run with a pm API; anything else is listed as a warning.
  4. Commit the files. Your teammates get them with git pull.

The full field mapping is in Postman collections to .http files. Without the extension, the command-line runner converts too: node plainwire.mjs import my-collection.json, with plainwire.mjs from the latest release.

When to stay with Postman

If your scripts send requests of their own (pm.sendRequest), load libraries with require() or use pm.visualizer, pm.cookies or pm.vault, or your team relies on mock servers, monitors or published documentation, Postman does those things and Plainwire does not. Plainwire runs the common pm.test, pm.expect and variable calls, not all of Postman’s sandbox (what is covered). Plainwire is for the everyday loop of writing, sending and checking requests, kept in plain files you own.

Questions

Is my data sent anywhere?

No. Plainwire makes no network calls of its own. The only traffic is the requests you send, to the URLs you wrote. See the privacy policy.

Can I keep Postman and use Plainwire for some projects?

Yes. Exporting does not change anything in Postman, and the two do not share storage.