Author here.<p>Some context: Speakeasy lets you generate SDKs from OpenAPI 3.x specs and now every user that generates a TypeScript SDK gets a Model Context Protocol (MCP) server bundled with it. This is available to users on both free and paid tiers.<p>I've been the primary maintainer of TypeScript SDK codegen and since launching it early last year, I made a bet on Zod for defining models and tying static TypeScript types to runtime validation. During that time, LLM function calling became a widespread feature and we saw that lots of folks preferred defining function arguments using Zod schemas and having something like `zod-to-json-schema` convert them to JSON Schema.<p>Fast forward to MCP's release and we noticed that the TypeScript SDK also accepts Zod schemas for defining tool arguments. The "gap" between generating a TypeScript SDK and going further to generate an MCP server was so small for us that we jumped right on it.<p>In terms of other interesting bits, the server is built out into a single JavaScript file using Bun's bundler. We also use stricli (<a href="https://bloomberg.github.io/stricli/" rel="nofollow">https://bloomberg.github.io/stricli/</a>) for type-safe CLI argument parsing and code structuring. We're also looking at building MCP servers out into standalone binaries which would remove the pre-requisite for node.js and npx when installing them. It's also possible to register additional custom tools and resources on top of what we generate so you're not locked out just because it's generated code. The generated tool themselves are also regular ES modules. You can skip over most things and import them from the SDK and into your own MCP server if you're building one yourself.