Synced OpenAPI Spec

I was soo chuffed when i found this project! It looks great, it read (almost) everything that i was looking for, a simple clean client for API development, local first with Git sync. As a team we’ve spent a long time looking for a Postman alternative and have been suprised and frustrated at the options out there, everything seemed to take the concept of a client too far, even pricing users out for features like Git support.

Unfortunately (for us), the only feature that Yaak doesnt support, that is a requirement of ours, is including OpenAPI in that local-first approach and through to Git sync.

To give you some background in why we need this, and why others might too:

Our documentation platform (Mintlify), like many options out there, support syncing of endpoints via an OpenAPI spec. This means a fully generated API docs site, try me features etc etc, all from a single file. This spec can also power MCP servers, something that is becoming quite dominant in AI. Meaning that a single spec file can power a number of big infrastructure pieces for an organisation, and be the central piece in the puzzle for an organisations AI strategy and more (amazing from a developers pov).

For a developer, OpenAPI specs solve a lot of process headache because of their adoption by 3rd party services, but it leaves another key puzzle piece remaining, how do we develop our apis, query endpoints as we go and ultimately build that OpenAPI spec and push it somewhere to feed all those other services?

If an API client existed that allowed us to build our endpoints, define parameters, describe that endpoint, generate and store request/response examples and ultimately commit those changes in the OpenAPI format, we’d be able to stitch together a ton of complex process very easily.

Some clients out there can export to OpenAPI, but thats a manual step each time a change is made, and makes an otherwise seamless pipeline/process manual and brittle.

I see there has been a request to support OpenAPI export, so taking that a step further, and auto-generating it for Git sync would hopefully be a minor task.

Will be keeping an eye on this project, as you are certainly on to something here. I also think with the growing dominance of MCP, it potential impact, and the number of service already out that that can convert OpenAPI into an MCP server, there is a real gap in the market on the side of creating and managing that spec for developers.

Hopefully this could be added to the roadmap. Do let me know if you wanted any more info about our use case (an apologies for the long feedback). Cheers!