The Problem
Getting started with MCP servers can be hard. Tools like guMCP streamline execution, but generating valid MCP server schemas from existing APIs still requires deep technical expertise, manual formatting, and guesswork. We needed a way to turn OpenAPI spec docs into MCP-compatible schemas, without requiring deep technical knowledge.
How we built it
Next.js 15 and React 18 for the frontend
TypeScript for type safety and maintainability
Tailwind CSS and Radix UI for a modern, responsive UI
Supabase for authentication, database, and row-level security Middleware to guard authenticated routes
We also built support for file parsing, clipboard input, and live schema rendering using OpenAPI parsers and custom MCP schema generation logic.
Accomplishments that we're proud of
A full-stack product that hides technical complexity while enabling powerful output
Successfully abstracting away MCP schema generation so users don’t need to worry about the internal format
Creating an interface that’s visually intuitive and developer-friendly
What we learned
How to design around real-world pain points in developer onboarding
Deepened our understanding of OpenAPI structures and schema translation
Learned how to design product flows that simplify advanced infrastructure concepts for everyday users
What's next for OpenAPI Schema to MCP Server
Support for editing schemas in-app with validation feedback
Auto-sync with API source URLs to regenerate schemas on changes
Shareable schema links and team collaboration features
Built With
- fastapi
- gumloop
- javascript
- mcp
- nextjs
- python
- railway
- redis
- supabase
Log in or sign up for Devpost to join the conversation.