MCP is here and I started to implement it into our code base. It was clunky, had bugs and was wondering if there was a product to convert your existing REST API spec into an MCP server. Everyone has an API spec and wouldn't it be great if all REST APIs out there are MCP ready with no code? Then I thought of building RapidMCP.
I'd love to add a feature where it takes an OpenAPI Swagger spec and then converts it to an MCP server for you. There are also some auth considerations.
Would love feedback/thoughts/comments from the community about whether this is a viable product?
Hi Joshua! I was trying to send a support ticket to you on the backend. Could you please check the form?
Also, how do I use the coupon code for the 3months after I signup to a paid plan?
Thanks!
It looks like using SSE to connect the MCP Server, but for now, SSE connect is unstable for connection, you need to reconnect after a while.😭
This is a smart direction — converting existing REST APIs to MCP with no code feels like a huge unlock, especially for teams that want to experiment without deep protocol-level refactors. Swagger/OpenAPI support is a must IMO — almost every modern API has a spec, and making that the entry point is super smart.
Auth is definitely the tricky part, especially with custom token logic or layered permissions — curious how you plan to abstract that cleanly without making it too rigid.
Overall though, love the idea. It feels like the kind of infrastructure tool that could quietly become essential if done right. Would definitely keep an eye on this.
Great to see this! I've been exploring solutions like this for @Hedy AI, so that users can have other AI tools easily tap into their meeting history. We'll probably give this a try in the coming week.
This hits exactly where MCP is still rough for most devs. Love the vision behind RapidMCP — turning existing OpenAPI specs into MCP servers would be a game-changer for anyone trying to “agentify” legacy systems without rebuilding them from scratch.
Auth is definitely a tricky area, especially if you’re dealing with token scopes or user-specific routing — would be curious how you’re thinking about handling things like OAuth2 flows or even internal API keys in an MCP context.
I’d 100% use this if it helps bridge the gap between traditional REST APIs and the emerging agent infrastructure. Excited to see where you take this!
@joshua_heslin Congrats on the launch! API to MCP is a straightforward connection but the tricky part is handling the many API specs and also MCP client configs. Curious to hear your thoughts on how to adapt to these!
