MCP development pipeline

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.

install

$npm install -g mcpkit-cli

Quick Start GitHub

4 templates10 CLI commandsbun · npm · pnpm

command pipeline / quick start

quick startbasic templatenpm path

$ npm install -g mcpkit-cli

$ mcpkit init hello-mcp --template basic --package-manager npm --yes

active stage

repository verified

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

client config

.vscode/mcp.json

package manager

npm

ready

$ cd hello-mcp

$ npm run dev

hello-mcp MCP server running on stdio

The problem

Building the server is only part of the job.

Raw MCP SDK boilerplate gets you to an entry file. It does not give you a complete developer workflow. `mcpkit` is most useful in the gaps around the server itself.

Project setup

Create files, package scripts, and the first entry point yourself.

Transport wiring

Choose stdio or HTTP and connect transport details correctly.

Validation

Catch obvious mistakes before runtime and editor integration.

Diagnostics

Check environment, SDK presence, structure, and config files.

Client configuration

Add working MCP client config instead of starting from scratch.

Release flow

Run tests, build, bump versions, and publish consistently.

Unified workflow

One toolkit, one command language, one visible path to shipping.

The commands are designed as a system rather than isolated utilities. You scaffold, run, test, validate, diagnose, build, and ship from the same toolchain.

init

dev

test

validate

doctor

build

ship

docs

check-env

completions

Interactive command explorer

Explore the actual CLI surface, not imagined marketing syntax.

Every command, option, and preview here is derived from the current repository.

command explorer

command / init

syntax

$ mcpkit init my-server --template basic --package-manager npm --yes

verified options

--template <template>--package-manager <pm>--yes

realistic output preview

ℹ Creating project: my-server

ℹ Template: basic

ℹ Package manager: npm

✔ Project created successfully!

Templates

Progress from minimal stdio to a fuller operational baseline.

The templates are not duplicates. Each one adds a verified layer of capability and generated structure.

stage 1stdio

basic

Start fast, learn the MCP shape, and run locally with the fewest moving parts.

src/index.ts
.vscode/mcp.json

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

Developer experience

More than scaffolding: the surrounding workflow is part of the product.

Development workflow

The generated projects come with watch-mode scripts, and the CLI exposes a `dev` command with inspector and test-watcher helpers.

Testing and validation

Use the generated Vitest scripts, `mcpkit test`, and `mcpkit validate` for quick checks from the terminal.

Diagnostics

`check-env` and `doctor` cover environment readiness, project structure, SDK presence, and MCP config discovery.

Inspector and debugging

`mcpkit dev --inspect` links to the official MCP Inspector instead of inventing another local debugging layer.

Build and ship

`build` and `ship` keep the release path close to the rest of the toolkit instead of leaving production steps disconnected.

Shell completions

Generate or install completions for bash, zsh, and fish directly from the CLI.

Generated project experience

See the actual project shape users get after `mcpkit init`.

generated structure / full template

package.json

tsconfig.json

.vscode/mcp.json

src/index.ts

src/auth.ts

src/logger.ts

src/health.ts

src/metrics.ts

eslint.config.js

.prettierrc

why the files exist

The generated structure is not just an entry file. The `full` template adds the surrounding workflow pieces developers usually end up hand-assembling later: auth wiring, logging, health checks, metrics, linting, and formatting.

The docs reference uses the real generated file set, and the template pages explain where the current implementation is strong and where it still has caveats.

src/index.ts wires routes, transport, auth, and metrics.
src/auth.ts holds bearer-token verification middleware.
src/health.ts returns uptime and version data.
src/metrics.ts stores in-memory counters and timing samples.

Quick Start

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 in `--yes` mode
• starts the generated server with `npm run dev`

Open the full Quick Start guide

install

$npm install -g mcpkit-cli

create

$mcpkit init hello-mcp --template basic --package-manager npm --yes

develop

$cd hello-mcp && npm run dev

Documentation bridge

Learn, reference, and troubleshoot without leaving the product experience.

The docs live in the same app, use the same visual system, and are written from verified command behavior and generated template output.

Open source

Open repository, visible code, real contribution paths.

No invented stats, no fabricated logos, no testimonial theater. Just the repository, the package, contribution docs, and the current roadmap in context.

Source code

Browse the monorepo and inspect the CLI source directly.

npm package

Install the current published package: mcpkit-cli.

Contributing

Read contribution guidelines before opening changes.

Documentation

Move from discovery into reference without leaving the app.

FAQ

Adoption questions answered from the current implementation.

mcpkit is a CLI toolkit for creating and working with TypeScript MCP servers. In the current repository it covers project creation, development helpers, testing, validation, diagnostics, docs generation, builds, publishing, and shell completions.

Why mcpkit

Build MCP servers with the workflow already wired in.

Generating client config

Building the server is only part of the job.

One toolkit, one command language, one visible path to shipping.

Explore the actual CLI surface, not imagined marketing syntax.

Progress from minimal stdio to a fuller operational baseline.

basic

http

auth

full

More than scaffolding: the surrounding workflow is part of the product.

Development workflow

Testing and validation

Diagnostics

Inspector and debugging

Build and ship

Shell completions

See the actual project shape users get after `mcpkit init`.

The shortest reliable path to a working MCP server.

Learn, reference, and troubleshoot without leaving the product experience.

Open repository, visible code, real contribution paths.

Adoption questions answered from the current implementation.

What is mcpkit, exactly?

Which template should I start with?

Can I use npm, pnpm, or Bun?

Is mcpkit only for local MCP servers?

Does `validate` do deep protocol validation?

Can I keep using the generated project without the CLI later?

Understand it. Try it. Keep going in the docs.