Hey Product Hunt! 👋 Solo maker here.

Karve started from a simple annoyance: my API requests already lived as .http files (the format Visual Studio, VS Code REST Client and JetBrains use) in my microservices' repos, but the moment they spread across projects there was no workspace for them, just a runner buried in each editor. That was quite annoying and every tool to launch them was slow and heavy (especially my daily driver - VS)

So I built a workspace, a tool, and made three stubborn choices:

1. Files stay files. Karve doesn't import your requests into a proprietary database. It organizes the .http/.rest files you already have, from any repo, without moving them. They keep diffing, branching, and reviewing like code.

2. Native or nothing. It's Windows native WinUI 3 app: cold start under 2 seconds, Mica themes, x64 and ARM64. No Electron shell, no cloud. Requests never leave your PC.

3. Your agent can drive it, without seeing your secrets. Karve ships a built-in MCP server, so Claude Code (or any MCP client) can find, run, fix, and author requests in your real workspace. But it only ever sees your requests as raw text with {{placeholders}} - resolved URLs, environment values, and stored history never cross to the agent. Off by default, because I'm not sure if it's coold or not, one toggle in Settings, localhost only. 90-second demo: https://youtu.be/qxPAWP8QY50

All of it is a one-time purchase (launch sale: $29.99, reg. $39.99) with a 15-day free trial.

MCP is included, and every 1.x update comes with it.

There are bunch of free client-side converters on the site (cURL/OpenAPI/HAR → .http), no purchase needed.

Eventually I'll move them into app, don't want to bloat it now.

I trying to keep scope limited: REST only today (WebSocket and Postman/cURL import are on the 1.1 roadmap), single-user, Windows only. Again, the last thing I want is more bloat

I'd love to hear how you keep API requests today, and what would make you move them into plain files.

I'm here all day. 🚢