create-typescript

This MCP server is a CLI scaffolder for quickly generating new MCP (Model Context Protocol) servers written in TypeScript. It lets you spin up a ready-to-develop MCP server project by invoking the generator with your desired server name and optional metadata. After generation, you’ll get a structured project containing the MCP server skeleton, ready to customize with your context models, handlers, and protocol logic. Use the included commands to install dependencies, build, and run in watch mode during development. The tooling emphasizes fast iteration for TypeScript-based MCP servers and aims to streamline boilerplate setup so you can focus on implementing your MCP-specific behavior.

Prerequisites:

• Node.js (recommended LTS) and npm installed
• Basic familiarity with TypeScript and MCP concepts

Install and scaffold a new server:

1. Create the server scaffold in a desired directory (example uses a folder named my-server): npx @modelcontextprotocol/create-server my-server

2. Change into the new server directory and install dependencies: cd my-server npm install

3. Build your server (TypeScript compilation): npm run build

4. (Optional) Run in watch mode to rebuild on file changes: npm run watch

5. (Optional) If you want to expose the local scaffold as a global binary during development: npm link

Notes:

• The generator creates a TypeScript-based MCP server scaffold you can customize. It does not publish a runnable server by itself; you’ll configure and run the generated project using the standard Node.js tooling provided by the scaffold.

Tips and common issues:

• Ensure you have a compatible Node.js version for the TypeScript project generated by the scaffold.
• If npm install fails due to network issues, retry or configure a registry proxy.
• The generated project typically includes npm scripts such as build and watch; use them to compile and iterate quickly.
• When linking locally (npm link), ensure you’re using the linked binary from the scaffolded project rather than the generator package.
• If you plan to publish or reuse this server, verify package.json metadata (name, version, description) matches your MCP deployment conventions.
• Check the README or generated docs inside the new server for any server-specific configuration options and environment variables.