Live data from Hacker News

Show HN: Superglue – open source API connector that writes its own code

github.com

31–40 of 49 posts

Re: Show HN: Superglue – open source API connector that writes its own code

#31
Once you have the OpenAPI specs, you can build an MCP server on top of that. Automatically. You don't have them ? There's MITM2Swagger[0] that will do it's best to infer it. Probably you'll need some manual adjustments, but still. And MCP servers can now be integrated with any LLM, not only Anthropic. While I appreciate your approach, how do you fight the MCPs?

[0] https://github.com/alufers/mitmproxy2swagger

Re: Show HN: Superglue – open source API connector that writes its own code

#32

Once you have the OpenAPI specs, you can build an MCP server on top of that. Automatically. You don't have them ? There's MITM2Swagger[0] that will do it's best to infer it. Probably you'll need some manual adjustments, but still. And MCP servers can now be integrated with any LLM, not only Anthropic. While I appreciate your approach, how do you fight the MCPs? [0] https://github.com/alufers/mitmproxy2swagger

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.

Re: Show HN: Superglue – open source API connector that writes its own code

#35
What are the limitations on usage? What's the approximate usage percentage, say, per kilotoken of context? Is there a point at which users are not allowed to query (profitably)?

Re: open source, what's your general attitude/commitment towards the community? Is it more like SQLite (no contributions accepted), or more like Rust (let's get everyone involved)?

Re: Show HN: Superglue – open source API connector that writes its own code

#36

Once you have the OpenAPI specs, you can build an MCP server on top of that. Automatically. You don't have them ? There's MITM2Swagger[0] that will do it's best to infer it. Probably you'll need some manual adjustments, but still. And MCP servers can now be integrated with any LLM, not only Anthropic. While I appreciate your approach, how do you fight the MCPs? [0] https://github.com/alufers/mitmproxy2swagger

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.

Re: Show HN: Superglue – open source API connector that writes its own code

#37

What are the limitations on usage? What's the approximate usage percentage, say, per kilotoken of context? Is there a point at which users are not allowed to query (profitably)? Re: open source, what's your general attitude/commitment towards the community? Is it more like SQLite (no contributions accepted), or more like Rust (let's get everyone involved)?

If you're self-hosting, you can bring your own model and there are no limitiations. For the hosted version, we currently do custom pricing agreements with our customers using this in prod, and keep it free for hobbyists within fair use limits. We still need to figure out what the boundaries will be, tbh.

On your open source question, we accept contributions from non-team-members and have done so in the past, particularly on bugs or new features on the backend.

Re: Show HN: Superglue – open source API connector that writes its own code

#38
post #29

Really cool project! I'm very bullish on LLMs for structured data. Curious - why did you decide to open source? It's neat to see a lot new YC open source companies. I'm curious why you thought open-sourcing superglue was strategically advantageous

Thanks! The primary reason is because we want folks to be able to run this locally and contribute to the project / fix issues as they come up. This is much harder when you have a black box tool and rely on our small team for support.

Because of the GNU General Public License, any project/startup that makes use of Superglue is required to open source all their code under the same license? I'm not a license/copyright expert, so I'm a bit fuzzy about how this is supposed to work.
Post reply on HN