I was looking into building an MCP server for Upstash when I realized we're duplicating work.
We already have OpenAPI specs. They contain everything agents need: tool names, descriptions, arguments, schemas. An MCP server would just be a thin wrapper around our backend, translating the same information into a different format.
So instead of building another server, I created a minimal CLI that creates tools directly from OpenAPI specs at runtime. No MCP server needed. It works. Agents can call our APIs using just the OpenAPI definition.
Next steps: Add Bearer and Basic Auth support (currently only OAuth works), and build an MCP stdio server so people can use local/remote OpenAPI files to create tools for their agents.
cahid_arda•1h ago
We already have OpenAPI specs. They contain everything agents need: tool names, descriptions, arguments, schemas. An MCP server would just be a thin wrapper around our backend, translating the same information into a different format.
So instead of building another server, I created a minimal CLI that creates tools directly from OpenAPI specs at runtime. No MCP server needed. It works. Agents can call our APIs using just the OpenAPI definition.
Next steps: Add Bearer and Basic Auth support (currently only OAuth works), and build an MCP stdio server so people can use local/remote OpenAPI files to create tools for their agents.
Code: https://github.com/CahidArda/spec2tools