typescript-mcp-server-generator

To scaffold a TypeScript MCP server, generate a project with package.json, tsconfig.json for ES modules, Express Streamable HTTP transport, and tool registration using zod@3 schemas for input validation. This provides a production-ready server with lifecycle and error handling.

The best way to create an MCP server in Node.js is using TypeScript with the @modelcontextprotocol/sdk, configuring either an Express Streamable HTTP or stdio transport, and defining validated tools with zod schemas to expose structured results to LLM integrations.

Yes, you can use stdio transport instead of Express for a local MCP server. The scaffolding supports both Express Streamable HTTP for integrations and stdio-based servers for lightweight CLI agents, both with lifecycle and error handling.

Yes, zod@3 is required to build validated tools for an MCP server in TypeScript. Tool registration patterns use zod schemas to enforce input and output validation, returning structured content alongside standard content results.

Generated MCP server projects include npm start and dev scripts using tsx or ts-node for rapid development. The setup provides developer ergonomics including a .gitignore file, ES module configuration, and testing instructions for quick deployment.

You should avoid Express Streamable HTTP transport when running lightweight CLI agents or local integrations that do not require network exposure. In those cases, use the stdio transport instead for direct, local communication without HTTP overhead.