Rename project to create-mcp-ts, bump to 0.3.1

Author: stephencme

README.md

@@ -1,16 +1,15 @@
-# mcp-init
+# create-mcp-ts
 
-![NPM Version](https://img.shields.io/npm/v/mcp-init)
+![NPM Version](https://img.shields.io/npm/v/create-mcp-ts)
 
-
-[packages/mcp-init](./packages/mcp-init/README.md)
+[packages/create-mcp-ts](./packages/create-mcp-ts/README.md)
 
 Create a new MCP server in TypeScript, batteries included.
 
 [packages/mcp-scripts](./packages/mcp-scripts/README.md)
 
-The build tools that power`mcp-init` projects.
+The build tools that power `create-mcp-ts` projects.
 
-[packages/mcpi-template-default](./packages/mcpi-template-default/README.md)
+[packages/mcp-ts-template-default](./packages/mcp-ts-template-default/README.md)
 
-Default project template for `mcp-init`.
+Default project template for `create-mcp-ts`.

package-lock.json

@@ -1,4 +1,4 @@
-.mcpi/
+.mcp-ts/
 dist/
 node_modules/
 

packages/mcp-init/.gitignore renamed to packages/create-mcp-ts/.gitignore

@@ -1,21 +1,21 @@
-# mcp-init
+# create-mcp-ts
 
 Create a new MCP server in TypeScript, batteries included.
 
 ## Getting started
 
 ```shell
-npx mcp-init your-mcp-server
+npm init mcp-ts your-mcp-server
 cd your-mcp-server
 npm run setup
 npm run dev
 ```
 
-`mcp-init` requires **zero build configuration** - it will automatically install everything you need to develop, build, and set up your MCP server.
+`create-mcp-ts` requires **zero build configuration** - it will automatically install everything you need to develop, build, and set up your MCP server.
 
 ### Set up your MCP server in Cursor, Windsurf, and Claude Desktop
 
-`mcp-init` can automatically configure your MCP server in Cursor, Windsurf, and Claude Desktop:
+`create-mcp-ts` can automatically configure your MCP server in Cursor, Windsurf, and Claude Desktop:
 
 ```shell
 npm run setup
@@ -42,11 +42,11 @@ For more details on how to set up MCP servers in Cursor, Windsurf, and Claude De
 
 ### Custom templates
 
-If you'd like to use a custom template, you can do so by passing the template npm package name or file path to the `npx mcp-init` command:
+If you'd like to use a custom template, you can do so by passing the template npm package name or file path to the `npx create-mcp-ts` command:
 
 ```shell
-npx mcp-init your-mcp-server --template=mcpi-template-default
-npx mcp-init your-mcp-server --template=file:/path/to/mcpi-template
+npx create-mcp-ts your-mcp-server --template=mcp-ts-template-default
+npx create-mcp-ts your-mcp-server --template=file:/path/to/mcp-ts-template
 ```
 
 ### Publishing your MCP server
@@ -61,7 +61,7 @@ If you plan to share your MCP server, you can publish it to npm:
 
 ## Ejecting from `mcp-scripts`
 
-The `mcp-scripts` package contains build tools for `mcp-init` projects - everything you'll need to develop, build, and set up an MCP server **without any additional configuration**.
+The `mcp-scripts` package contains build tools for `create-mcp-ts` projects - everything you'll need to develop, build, and set up an MCP server **without any additional configuration**.
 
 Under the hood `mcp-scripts` uses [tsup](https://github.com/egoist/tsup) and [esbuild](https://github.com/evanw/esbuild), lightweight, battle-tested utilities that are well-suited for production-grade TypeScript projects.
 
@@ -108,11 +108,11 @@ which node
 
 Make sure to update your MCP config in each client (Cursor, Windsurf, or Claude Desktop) with the correct absolute path to the Node.js binary you want to use.
 
-For any other issues, please [open an issue here](https://github.com/stephencme/mcp-init/issues/new).
+For any other issues, please [open an issue here](https://github.com/stephencme/create-mcp-ts/issues/new).
 
 ## Philosophy
 
-`mcp-init` is designed to be a batteries-included, "it just works" experience for MCP server developers.
+`create-mcp-ts` is designed to be a batteries-included, "it just works" experience for MCP server developers.
 
 - **Batteries included**: there is only one build dependency, `mcp-scripts`. It uses tsup, esbuild, and other amazing open source projects, but provides a curated experience on top of them.
 - **Zero configuration**: you don't need to configure anything. A reasonably good configuration is handled for you so you can focus on writing code.

packages/mcp-init/README.md renamed to packages/create-mcp-ts/README.md

@@ -1,13 +1,13 @@
 {
-  "name": "mcp-init",
-  "version": "0.3.0",
+  "name": "create-mcp-ts",
+  "version": "0.3.1",
   "description": "Create a new MCP server in TypeScript, batteries included.",
   "author": "stephencme",
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/stephencme/mcp-init.git",
-    "directory": "packages/mcp-init"
+    "url": "https://github.com/stephencme/create-mcp-ts.git",
+    "directory": "packages/create-mcp-ts"
   },
   "keywords": [
     "create",

packages/mcp-init/jest.config.js renamed to packages/create-mcp-ts/jest.config.js

@@ -2,10 +2,10 @@ import { execSync } from "child_process";
 import fs from "fs-extra";
 import path from "path";
 
-describe("mcp-init", () => {
-  const testProjectDir = "./.mcpi/test-mcp-server";
+describe("create-mcp-ts", () => {
+  const testProjectDir = "./.mcp-ts/test-mcp-server";
   const testProjectName = path.basename(testProjectDir);
-  const templatePath = "../mcpi-template-default";
+  const templatePath = "../mcp-ts-template-default";
 
   afterEach(() => {
     // Clean up test directory after each test

packages/mcp-init/package.json renamed to packages/create-mcp-ts/package.json

@@ -77,7 +77,7 @@ async function run() {
   printCreatingServer(resolvedProjectPath);
 
   // Determine which template to use (default or custom)
-  const templateName = options.template || "mcpi-template-default";
+  const templateName = options.template || "mcp-ts-template-default";
   printUsingTemplate(templateName);
 
   // Copy template contents
@@ -190,7 +190,7 @@ async function run() {
     await executeCmd("git", ["add", "-A"], resolvedProjectPath);
     await executeCmd(
       "git",
-      ["commit", "-m", "Initial commit from mcp-init"],
+      ["commit", "-m", "Initial commit from create-mcp-ts"],
       resolvedProjectPath
     );
     console.log("Created git commit.");

packages/mcp-init/src/index.test.ts renamed to packages/create-mcp-ts/src/index.test.ts

@@ -42,14 +42,14 @@ const helpString = () => `Only ${chalk.green(
 
     A custom ${chalk.cyan("--template")} can be one of:
       - a custom template published on npm: ${chalk.green(
-        "mcpi-template-default"
+        "mcp-ts-template-default"
       )}
       - a local path relative to the current working directory: ${chalk.green(
         "file:../your-custom-template"
       )}
 
     If you have any problems, do not hesitate to file an issue:
-      ${chalk.cyan("https://github.com/stephencme/mcp-init/issues/new")}`;
+      ${chalk.cyan("https://github.com/stephencme/create-mcp-ts/issues/new")}`;
 
 // Specify project directory string
 const specifyProjectDirectoryString = (programName: string) =>