Beta · Browser-only codegen
OpenAPI → MCP server generator
Paste any OpenAPI 3.x spec — get a runnable Node.js MCP server with one tool per endpoint, ready to wire into Claude Desktop, Cursor, Windsurf or Continue.
Spec
—
Version
—
Tools
0
Errors
0
Paste OpenAPI 3.x JSON
JSON only for now. Convert YAML to JSON first (one-liner with js-yaml) — YAML support is planned.
Nothing generated yet
Paste an OpenAPI spec on the left, or click "Load sample".
What you get
server.js
A pure ES-module Node.js MCP server. One tool per OpenAPI operation. Stdio transport, no transpilation.
package.json
Single dependency:
@modelcontextprotocol/sdk. Ready tonpm install& run.claude_desktop_config.json
Drop-in config snippet. Replace the placeholder token, restart Claude, done.
README.md
Tools list, install & run instructions, env var reference. Drop into your repo as-is.
OpenAPI generator — FAQ
What does the generator produce?
A runnable Node.js MCP server: server.js (one tool per OpenAPI operation), package.json (with @modelcontextprotocol/sdk), README.md, and a ready-to-paste Claude Desktop config. Stdio transport, Node 20+.
How does authentication work?
The generated server reads a Bearer token from a per-server env var (e.g. PETSTORE_API_TOKEN). Replace it in claude_desktop_config.json with your real key. Custom auth schemes (basic, API key in header, OAuth) require a small edit to AUTH_HEADERS.
Why JSON only, not YAML?
Browser-side YAML parsing is doable but adds a dependency. Use any one-liner converter (`npx js-yaml spec.yml > spec.json`) for now — proper YAML support is on the roadmap.
Can I extend the generated code?
Yes — it is plain ES modules, no transpilation. Add response post-processing, custom error handling or rate limiting directly in server.js. We deliberately keep the output close to the metal.
Does anything leave my browser?
No. The OpenAPI spec stays local — parsing, codegen and copy/paste all happen client-side.