Thanks for sharing! We're taking a bit of a different angle here. The APIs we are looking at are not the ones that websites are using, but rather then ones you would typically integrate with when thinking about data integrations. Also, while you could use superglue as an MCP server, the usecases we see right now are less in the AI / agent world but rather in the workflow / ETL / onboarding world.

That being said, the mitmproxy2swagger approach is really really cool as an alternative to mindless scraping.

And with MCP, the idea is that the agent can translate a natural language instruction into the specific API request and then translate the schema into whatever structured output format you want? Is there anything that Superglue does that you wouldn't get somewhat out of the box using agents and MCP? I'm not too familiar with MCP so still trying to understand how it compares to this sort of thing.

my personal understanding (anyone feel free to correct me here) of MCP is that it is basically a standardized interface for tool use. So, if you as an API provider (e.g. stripe) want agents to connect to your API, you can offer an MCP server that serves as a middleman between you and the agent. What we fundamentally do is serve also as a middleman, but not (primarily, yet) for agents, but for normal (non-AI) applications that would otherwise need to use the REST/SOAP/whatever API with a bunch of integration code. Also, MCP does not do any data transformation, that would be on the agent to do.

> Once you have the OpenAPI specs, you can build an MCP server on top of that. Automatically.

What's the route to doing this automatically? Is there some tool for doing this?