Create-MCP-Kit

A CLI tool to create MCP (Model Context Protocol) applications with ease.

[![][npm-release-shield]][npm-release-link] [![][codecov-shield]][codecov-link] [![][github-release-date-shield]][github-release-date-link] [![][github-action-build-shield]][github-action-build-link] [![][github-license-shield]][github-license-link]

Features

• 🚀 Quick project scaffolding
• 📦 TypeScript support out of the box
• 🛠️ Built-in development tools
• 🔧 Configurable project templates
• 🌐 Multiple Transport Modes (stdio/streamable-http/sse)
• 📚 Comprehensive APIs

Usage

npm create mcp-kit@latest

or

yarn create mcp-kit@latest

or

pnpm create mcp-kit@latest

Project Types

create-mcp-kit supports generating two types of projects:

MCP Server

Create an MCP server that provides tools, resources, and prompts for MCP clients.

Server Project Structure

The generated server project will have the following structure:

├── src/
│   ├── tools/             # MCP tools implementation
│   │   ├── index.ts       # Tools registration
│   │   └── register*.ts   # Individual tool implementations
│   ├── resources/         # MCP resources implementation
│   │   └── index.ts       # Resources registration
│   ├── prompts/           # MCP prompts implementation
│   │   └── index.ts       # Prompts registration
│   ├── services/          # Server implementations
│   │   ├── stdio.ts       # STDIO transport implementation
│   │   └── web.ts         # Streamable HTTP and SSE transport implementation
│   └── index.ts           # Entry point
├── tests/                 # Test files (optional)
├── scripts/               # Build and development scripts
├── .github/               # GitHub Actions workflows (optional)
├── .husky/                # Git hooks (optional)
├── .prettierrc            # Prettier configuration (optional)
├── changelog-option.js    # Conventional changelog config (optional)
├── commitlint.config.js   # Commit message lint rules (optional)
├── eslint.config.js       # ESLint configuration (optional)
├── lint-staged.config.js  # Lint-staged configuration (optional)
├── vitest.*.ts            # Vitest configuration (optional)
└── package.json

Server Development Scripts

• npm run dev - Start the development server in stdio mode
• npm run dev:web - Start the development server in web mode
• npm run build - Build the project
• npm run test - Run tests (if vitest plugin is selected)
• npm run coverage - Generate test coverage report (if vitest plugin is selected)
• npm run lint - Run linting (if style plugin is selected)

MCP Client

Create an MCP client that connects to MCP servers and uses their tools, resources, and prompts.

Client Project Structure

The generated client project will have the following structure:

├── src/
│   └── index.ts           # Entry point with transport implementations
├── tests/                 # Test files (optional)
├── scripts/               # Build and development scripts
├── .github/               # GitHub Actions workflows (optional)
├── .husky/                # Git hooks (optional)
├── .prettierrc            # Prettier configuration (optional)
├── changelog-option.js    # Conventional changelog config (optional)
├── commitlint.config.js   # Commit message lint rules (optional)
├── eslint.config.js       # ESLint configuration (optional)
├── lint-staged.config.js  # Lint-staged configuration (optional)
├── vitest.*.ts            # Vitest configuration (optional)
└── package.json

Client Development Scripts

• npm run dev - Start the client in development mode
• npm run build - Build the project
• npm run test - Run tests (if vitest plugin is selected)
• npm run coverage - Generate test coverage report (if vitest plugin is selected)
• npm run lint - Run linting (if style plugin is selected)

Features

MCP Server Features

Transport Modes

MCP Server supports three tr

... View full README on GitHub