Typescript MCP Server Generator

TypeScript MCP server generator

Generate a production-ready Model Context Protocol server in TypeScript using MCP TypeScript SDK v2, explicit transport selection, full Zod schemas, typed tool handlers, and runnable project commands.

When to invoke

• "Generate a TypeScript MCP server."
• "Create an MCP server with tools and resources."
• "Build an HTTP MCP server in Node."
• "Migrate this MCP server from v1 to v2."
• "Add stdio transport to a TypeScript MCP project."

Prerequisites and context

• Target Node.js 20+ and ESM-first TypeScript with "type": "module".
• Use MCP TypeScript SDK v2 focused packages; the v1 monolithic @modelcontextprotocol/sdk package is retired.
• Choose either HTTP Streamable HTTP transport or stdio. SSE and WebSocket transports were removed in v2 and must not be generated.

Package and runtime choices

Project structure

mcp-server/
├── package.json
├── tsconfig.json
├── .gitignore
├── README.md
└── src/
    ├── index.ts
    ├── server.ts
    ├── tools/
    │   └── greet.ts
    ├── resources/
    ├── prompts/
    └── config.ts

Initialize with npm init, install runtime dependencies such as @modelcontextprotocol/server, zod@^4.2, and the chosen transport package, then add dev dependencies such as tsx and typescript.

Server implementation rules

server.registerTool('greet', {
  title: 'Greet user',
  description: 'Greet user',
  inputSchema: z.object({ name: z.string() })
}, async ({ name }, ctx) => {
  return {
    content: [{ type: 'text', text: `Hello, ${name}!` }],
    structuredContent: { greeting: `Hello, ${name}!`, requestId: ctx.mcpReq.id }
  };
});

Resources, prompts, and advanced features

Transport configuration

Migration from v1

1. Run the official codemod:

   npx @modelcontextprotocol/codemod@latest v1-to-v2 .
   

2. Search for @mcp-codemod-error markers that need manual judgment.

3. Choose the v2 transport; do not recreate SSE or WebSocket.

4. Replace McpError + ErrorCode checks with ProtocolError, SdkError, or SdkHttpError; HTTP status is error.status, not error.code.

5. Remove deprecated Server.createMessage(), listRoots(), sendLoggingMessage(), and roots/sampling/logging capability fields from new code.

Testing guidance

• Add scripts for npm start, npm run dev, npm run build, and npm test when the generated project includes tests.
• Run the server with npm start or npx tsx src/index.ts.
• Inspect with npx @modelcontextprotocol/inspector.
• Include example tool invocations and expected content/structuredContent output in README.md.

Resource/Prompt generation may be included when useful. Stdio examples should import StdioServerTransport; stdio-based servers must keep stdout protocol-clean. Use TypeScript/Node.js project defaults, high-level McpServer APIs, async/await, and try-catch around external work. Remember that v1 called the handler context extra; v2 replaces it with ctx. Install adapter peers explicitly, for example npm install @modelcontextprotocol/express express. Migration command spelling must remain npx @modelcontextprotocol/codemod@latest v1-to-v2 .. A simple development command may be npx tsx server.ts. Schema examples may be shown as z.object({...}); do not pass raw { name: z.string() } shapes.

Output template

## TypeScript MCP server result

**Status:** generated | migrated | blocked
**Transport:** http | stdio
**Runtime:** Node.js 20+

| Artifact | Path | Notes |
| --- | --- | --- |
| Package config | `package.json` | `<dependencies/scripts>` |
| Server entry | `src/index.ts` | `<transport>` |
| Tools | `src/tools/<tool>.ts` | `<schemas/results>` |
| Docs | `README.md` | `<run and inspector commands>` |

**Commands**
- `npm install ...`: <pass/fail/not run>
- `npm run build`: <pass/fail/not run>
- `npx @modelcontextprotocol/inspector`: <usage documented/not run>

Quality gate

• Project uses Node.js 20+, TypeScript, and "type": "module" unless the user requested otherwise.
• v2 packages are used: @modelcontextprotocol/server, transport package, @modelcontextprotocol/core when schemas are needed, and zod@^4.2.
• No new SSE, WebSocket, v1 .tool() signatures, raw schema shapes, McpError, ErrorCode, StreamableHTTPError, Server.createMessage(), listRoots(), sendLoggingMessage(), roots, sampling, or logging capability fields are generated.
• At least one useful tool has a full Zod input schema, error handling, content, and structuredContent.
• Transport configuration includes lifecycle, environment, and HTTP/stdout details.
• README includes run commands, MCP Inspector command, HTTP URL when relevant, and example tool invocations.