RapidMCP
Convert your REST API into an MCP Server in minutes!
238 followers
RapidMCP convert your REST API into MCP Servers in minutes! No code required.
Subscribe
Sign in
238 followers
RapidMCP convert your REST API into MCP Servers in minutes! No code required.
RapidMCP
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?
Elisi : AI-powered Goal Management App
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!
RapidMCP
@williamrobertscott Fantastic feedback. Thanks for taking the time to comment.
I'd be more than happy to share additional details or provide any setup guidance if you are keen to try it out. Contact me on linkedin/socials if that's something of interest.
Cheers
@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!
RapidMCP
@thefullstack Excellent questions. I was thinking of building a Swagger OpenAPI spec convertor. Allowing a yaml file (with versioning) to be transformed into a running MCP server - this allows the builder to 'config only' the connections between an MCP server and their API.
When it comes to authentication, the simple approach to use existing API key/token scenarios but I acknowledge this may solve only some scenarios. Making RapidMCP multi-tenant with verifying user session via IdP is certainly a tricky problem and one I'm eager to explore as the use-cases come.
MCP Server config spec allows passing environment variables, these will be available in the templating section in RapidMCP so if the AI Agent can pass user context into the MCP server spec, then I'll be able to set up a tenant configuration on the RapidMCP side for tool invocation.
Thanks for your interest in RapidMCP - as you know, AI and MCP is rapidly evolving with many unknowns still.
@joshua_heslin That's a very detailed response. Appreciate it!
@joshua_heslin @thefullstack I'm working also on a product to generates openapi spec based on API traffic https://www.producthunt.com/products/doks-io :D