Hey, just clarify the case. You can directly read Swagger or OpenAPI Specification (OAS) files.

OK. Unflagged.

So this is about web APIs? I dislike that the broad term "API" has started to be used as shorthand for "HTTP API" (and probably REST-ish HTTP APIs specifically). It wastes people's time trying to figure out if something is of interest to them. Not everyone in tech is building web apps.

Fair point. I think the title can be more accurate by changing API into "REST API". Since I cannot edit the title as of now, I hope mod could change the title to be more accurate.

For more context, this tool can generate an MCP Server from an OpenAPI/Swagger file that describes a REST API. This does not include SOAP APIs, GraphQL, or other APIs that use the HTTP protocol.

Nobody on this planet builds REST APIs. It's not worth explaining what REST actually means. It is a waste of time.

HTTP API is the correct phrase.

That's why I tend to say "REST-ish" because there is a difference between those and things like GraphQL or RPC style APIs which can also use HTTP.

HTTP APIs are APIs that rely on HTTP semantics (so not GraphQL). And the only difference between what you call "REST-ish" and "RPC-style" is "POST /messages" vs "POST /createMessage" anyway.

You can directly read Swagger or OpenAPI specification files without Apidog projects, like this:

npx apidog-mcp-server --oas https://petstore.swagger.io/v2/swagger.json or npx apidog-mcp-server --oas ～/data/petstore/swagger.json

Oh so it's like this? Sorry, I was confused because your npmjs page explicitly says that the tool is for Apidog projects.