Karve is a native Windows API client designed for developers who manage their API requests using plain .http or .rest files. It provides a centralized workspace to organize these requests from various repositories, allowing for efficient environment switching and maintaining a searchable history. The core philosophy of Karve is to keep your request files on disk, ensuring they remain Git-friendly for version control and collaboration.
The problem Karve addresses stems from the fragmentation of API requests across different projects and editors. Developers often have their API requests defined as .http files within their microservices' repositories. However, when these requests are spread across multiple projects, there's no unified workspace to manage them, leading to a cumbersome experience where runners are buried within individual editors. This inefficiency, especially within heavy IDEs like Visual Studio, prompted the creation of Karve.
One of Karve's key features is its commitment to keeping files as files. Instead of importing requests into a proprietary database, Karve organizes the existing .http/.rest files directly from your repositories. This approach ensures that your requests can be diffed, branched, and reviewed just like any other code, maintaining a seamless workflow with your version control system.
Karve is built as a native Windows application using WinUI 3. This native approach ensures a fast cold start time, under 2 seconds, and supports Windows features like Mica themes. It is available for both x64 and ARM64 architectures. Crucially, Karve does not use an Electron shell or rely on cloud services, meaning your requests never leave your local machine, enhancing security and privacy.
Another significant capability is Karve's built-in MCP (Meta Call Protocol) server. This allows agents like Claude Code, or any other MCP client, to find, run, fix, and author requests within your actual workspace. However, Karve ensures that the agent only sees the requests as raw text with placeholders, and resolved URLs, environment values, and stored history are never exposed to the agent. This feature is off by default and operates on localhost only, providing a secure way to integrate AI assistance with your API development workflow.
Karve operates on a straightforward methodology: it acts as a workspace and a runner for your existing .http/.rest files. By leveraging the plain text format of these files, it avoids the complexities of proprietary formats and databases. The application focuses on providing a fast, native Windows experience, prioritizing local execution and Git integration.
The benefits for users include a streamlined API request management process, improved efficiency due to fast startup times, and enhanced security by keeping all request data local. The Git-friendly nature of the files also promotes better collaboration and version control practices.
Karve can be used in various scenarios, such as managing API requests for microservices scattered across different repositories, quickly testing endpoints without leaving your IDE's context, or integrating AI agents to help author and debug API calls securely. Developers can also use the free client-side converters to transform cURL, OpenAPI, or HAR files into the .http format.
Karve is a single-user, Windows-only application. It is available as a one-time purchase, with a launch sale price of $29.99 (regularly $39.99), and includes a 15-day free trial. All 1.x updates are included with the purchase. The product currently focuses on REST APIs, with WebSocket and Postman/cURL import planned for version 1.1.
In summary, Karve offers Windows developers a fast, native, and Git-friendly API client that organizes existing .http files, enhances security by keeping data local, and provides a seamless integration for AI-assisted development.