G12789/mcp-quickstart

npm create mcp-quickstart@latest my-server
npx mcp-quickstart petstore-mcp --from-openapi https://petstore3.swagger.io/api/v3/openapi.json
npx mcp-quickstart edge-server --transport cloudflare -y

Usage

• •cd weather-server && npm install && npm run dev && npm run inspect && npm test
• •API-to-server: npx mcp-quickstart my-api --from-openapi spec.json, set API_BASE_URL/.env auth, npm run dev
• •edge: npx mcp-quickstart edge-server --transport cloudflare -y; npm run deploy, then point Cursor/Claude at the /mcp URL

Key features

• ✓both TypeScript and Python templates (stdio + streamable HTTP)
• ✓OpenAPI 3.x → one typed MCP tool per operation, bodies expanded into per-field zod types ($ref/nested/arrays/enums resolved), plain editable generated TS
• ✓--from-curl turns a single curl command into an MCP tool; auth headers moved to .env
• ✓Cloudflare Workers deploy target (createMcpHandler, stateless, free plan, ~ms cold starts) — also combined API→edge in one command
• ✓ships tool ping + text_stats, resource greeting://{name}, prompt summarize; pure tools.ts keeps logic testable
• ✓tests green out of the box; .env.example/.gitignore/sane tsconfig included
• ✓templates/<language>-<transport>/ with _-prefixed files renamed on generation

Best for

Developers who want a runnable, tested MCP server (or an OpenAPI/curl → MCP bridge, optionally deployed to Workers) instead of an empty skeleton.

Caveats

• ⚠scaffolder, not a runtime — generated code is what you run and own
• ⚠Cloudflare Workers path is a gateway for API orchestration, not a GPU/model host
• ⚠Python output for OpenAPI/curl-generated servers still on the roadmap