// free tool
Turn your API into agent tools.
Paste an OpenAPI 3.x spec URL — or the spec itself. Get back a complete MCP server with one typed tool per operation, ready to install into Claude Desktop or Cursor.
Questions
What exactly do I get?
A complete TypeScript MCP server: package.json, tsconfig, a stdio entrypoint, one typed tool file per OpenAPI operation with Zod input schemas, a shared HTTP client, .env.example with auth stubs, and a README including the Claude Desktop config snippet. It compiles and runs as-is.
Is it production-ready?
No, and we won't pretend otherwise. It has no credentials, retry policy, pagination handling or rate limiting. A generator can't know your auth secrets or which environment you're targeting. Think of it as the first day of work done for you, not the last.
How do operations become tools?
One MCP tool per operation that has an operationId, named in snake_case. Path, query and body parameters flatten into a single Zod input schema, with conflicting names prefixed by location. Operations without an operationId are skipped and reported — models can't reliably pick tools named after a method and path.
What about $refs?
Internal refs (#/components/…) are dereferenced. External and remote refs are deliberately not followed — that would mean fetching arbitrary further URLs, which is both a performance and a security problem. Operations depending on one are skipped and listed.
Swagger 2.0 or YAML?
Neither yet. Swagger 2.0 is detected and reported rather than silently mis-generated from. For YAML, convert to JSON and use the paste tab.
Are there limits?
The first 30 operations are generated; anything beyond that is listed as skipped. Specs must be under 5MB.
// ready_when_you_are
Let's build your agentic advantage
Tell us what should be automated, connected or sold. We'll map the fastest path from idea to a production system.