create -kit

This MCP server kit provides a production-ready TypeScript MCP server scaffold that uses the stdio transport. The generated project builds to a dist/index.js file and is intended to be run locally or integrated with an MCP client (for example Claude Desktop) via a standard MCP configuration. To use it, first scaffold and build your server, then point your MCP client at the compiled entry point.

Typical workflow:

• Build the server: npm run build
• Run locally (during development): node dist/index.js
• Configure an MCP client to connect to the server using the generated mcpServers configuration (for example, the provided Minimal Claude Desktop config shows how to reference the built server).

Prerequisites:

• Node.js v18 or newer
• Git
• npm (or pnpm/yarn) for installing dependencies

Installation steps:

1. Clone the scaffold repository (or install via npm if applicable): git clone https://github.com/Epi-1120/create-mcp-server-kit cd create-mcp-server-kit

2. Install dependencies for the scaffold (or use the published tool): npm install

3. Create a new MCP server project from the template (example name: my-mcp-server): npm run create -- my-mcp-server

4. Navigate into the new server project and install its dependencies: cd my-mcp-server npm install

5. Build and run the server for development: npm run build node dist/index.js

If you prefer using npx to generate directly from the template, you can also run: npx create-mcp-server-kit@latest my-mcp-server cd my-mcp-server npm install npm run build node dist/index.js

Notes and tips:

• The default template is ts-stdio (TypeScript with stdio transport). You can extend it with additional tools and transports as needed.
• After building, the server is typically run with: node dist/index.js. Your MCP client should point to this executable via the mcpServers configuration.
• If you move the server or rename files, ensure the configured path in the mcpServers entry (dist/index.js) remains accurate.
• For environment variables or advanced configuration, consider adding variables like MCP_LOG_LEVEL, MCP_PORT, or any client-specific settings in your deployment environment.
• If you encounter MODULE_NOT_FOUND on Windows, run the CLI entry file directly via node ./bin/create-mcp-server-kit.js <name> as shown in the project guidance.