stage 1stdio
basic
Start fast, learn the MCP shape, and run locally with the fewest moving parts.
- src/index.ts
- .vscode/mcp.json
MCP server generator CLI
Build MCP servers with the workflow already wired in.
The create-next-app for MCP servers. Scaffold, develop, test, validate, diagnose, document, build, and ship from one toolkit instead of assembling the workflow yourself.
4 templates10 CLI commandsbun · npm · pnpm
terminal
$ npm install -g mcpkit-cli
$ mcpkit init hello-mcp --template basic --package-manager npm --yes
active stage
Generating client config
The generated client configuration is intentionally explicit. Today the templates create `.vscode/mcp.json`; the docs avoid claiming other generated client configs.
template
basic
transport
stdio
config
.vscode/mcp.json
package
npm
ready
$ cd hello-mcp
$ npm run dev
hello-mcp MCP server running on stdio
Commands this repo actually ships
Read the docsEvery command, option, and preview here is derived from the current repository.
The CLI is the main product. These are the commands you run every day.
create
$mcpkit init hello-mcp --template basic --package-manager npm --yes
dev
$mcpkit dev --transport http --port 3100 --inspect
test
$mcpkit test
validate
$mcpkit validate
doctor
$mcpkit doctor
build
$mcpkit build
ship
$mcpkit ship
docs
$mcpkit docs
check-env
$mcpkit check-env --json
completions
$mcpkit completions --install
The create flow is the main product
One command to scaffold, configure, and run.
mcpkit init asks the right questions and writes a runnable project. You choose the template, package manager, and project name — the rest is wired for you.
create
$mcpkit init hello-mcp --template basic --package-manager npm --yes
Interactive setup
The init command guides you through project name, template, transport, package manager, and optional features. Accept defaults with --yes for instant scaffolding.
Generated project structure
Each template produces a complete, runnable project with package scripts, TypeScript config, and version control files. No manual wiring required.
Inspector integration
mcpkit dev --inspect opens the official MCP Inspector — no custom debugging layer invented.
Dev workflow
Generated projects include watch-mode scripts and a dev command with inspector and test-watcher helpers built in.
Client config
Templates generate .vscode/mcp.json so MCP clients discover your server automatically.
Package manager detection
The ship command detects your package manager from the lock file and uses the correct publish command — npm, pnpm, or bun.
Templates
Pick the template before scaffolding.
Each template adds a verified layer of capability. Start minimal and upgrade when needed.
stage 2Streamable HTTP
http
Expose an HTTP MCP endpoint with home and health routes on port 3100.
- src/index.ts
- .vscode/mcp.json
stage 3HTTP + bearer auth
auth
Protect /mcp with bearer-token verification and a separate auth helper.
- src/index.ts
- src/auth.ts
- .vscode/mcp.json
stage 4HTTP + auth + ops
full
Add metrics, structured logging, health checks, linting, and formatting config.
- src/index.ts
- src/auth.ts
- src/logger.ts
- src/health.ts
- src/metrics.ts
Quick StartOpen the full Quick Start guide
The shortest reliable path to a working MCP server.
This path uses the current package name and an explicit npm package-manager choice, so it remains usable even if you do not have Bun installed yet.
what happens
- installs the published CLI package
- scaffolds the verified basic template
- installs dependencies automatically with --yes
- starts the generated server with npm run dev
install
$npm install -g mcpkit-cli
create
$mcpkit init hello-mcp --template basic --package-manager npm --yes
develop
$cd hello-mcp && npm run dev
MVP scope is intentional
Start with MCP structure, not auth or database opinions.
The current CLI generates simple request handlers, modules, docs, config, and project scaffolds. Auth, databases, ORMs, and other infrastructure are planned for future iterations.
What mcpkit does now
- Project scaffolding with 4 verified templates
- Development workflow with dev, test, build, ship commands
- Validation and diagnostics
- Client config generation
- Shell completions
Roadmap
- Auth and bearer token verification
- Database and ORM integration
- Structured logging and metrics
- Docker and deployment configs
- Extended validation protocols
Latest changelog
0.2.0 — Landing page redesign, CSS fixes, custom domain deployment.
Final CTA
Understand it. Try it. Keep going in the docs.
The shortest path starts with the install command, continues through Quick Start, and stays grounded in the repository-backed docs.