Skip to content
Back to search

mcp-kit

An interactive CLI for scaffolding ready-to-develop MCP servers and clients in TypeScript or JavaScript.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/my-mcp-hub/mcp-kit with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/my-mcp-hub/mcp-kit'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/my-mcp-hub--mcp-kit/badge.svg)](/listings/my-mcp-hub--mcp-kit)

HTML

<a href="/listings/my-mcp-hub--mcp-kit"><img src="/api/listings/my-mcp-hub--mcp-kit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Run the CLI with your package manager:

npm create mcp-kit@latest
pnpm create mcp-kit
yarn create mcp-kit

`bun create mcp-kit` and `deno init --npm mcp-kit` are also supported.

The interactive setup asks for:

| Choice | Options | | ------------ | ------------------------------------------------------------------------------------------------------- | | Project type | MCP Server · MCP Client | | Language | TypeScript · JavaScript | | Transport | STDIO · Streamable HTTP · both | | Template | Standard · Custom | | Plugins | GitHub Actions · Vitest · MCP Inspector (server) · ESLint/Prettier/Lint-staged · Commitlint · Changelog | | Dependencies | Install now · install later |

After generation:

cd mcp-server-starter
npm run dev

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 162 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <a href="https://my-mcp-hub.github.io/mcp-kit/" target="_blank" rel="noopener noreferrer">
  3. <img width="960" src="./docs/public/readme-hero.webp" alt="mcp-kit CLI generating a ready-to-develop MCP project" />
  4. </a>
  5. </p>
  6. <h1 align="center">mcp-kit</h1>
  7. <p align="center">
  8. An interactive CLI for scaffolding ready-to-develop Model Context Protocol servers and clients.
  9. </p>
  10. <p align="center">
  11. <a href="https://my-mcp-hub.github.io/mcp-kit/">Documentation</a>
  12. ·
  13. <a href="https://my-mcp-hub.github.io/mcp-kit/guide/getting-started">Getting started</a>
  14. ·
  15. <a href="https://github.com/my-mcp-hub/mcp-kit/issues">Issues</a>
  16. ·
  17. <a href="./packages/create-mcp-kit/CHANGELOG.md">Changelog</a>
  18. </p>
  19. <p align="center">
  20. <a href="https://www.npmjs.com/package/create-mcp-kit"><img src="https://img.shields.io/npm/v/create-mcp-kit?color=1677FF&labelColor=black&logo=npm&logoColor=white&style=flat-square" alt="npm version" /></a>
  21. <a href="https://github.com/my-mcp-hub/mcp-kit/actions/workflows/build.yml"><img src="https://img.shields.io/github/actions/workflow/status/my-mcp-hub/mcp-kit/build.yml?branch=main&color=1677FF&label=build&labelColor=black&logo=githubactions&logoColor=white&style=flat-square" alt="build status" /></a>
  22. <a href="https://codecov.io/gh/my-mcp-hub/mcp-kit"><img src="https://img.shields.io/codecov/c/github/my-mcp-hub/mcp-kit?color=1677FF&labelColor=black&logo=codecov&logoColor=white&style=flat-square" alt="test coverage" /></a>
  23. <a href="./LICENSE"><img src="https://img.shields.io/github/license/my-mcp-hub/mcp-kit?color=1677FF&labelColor=black&style=flat-square" alt="MIT license" /></a>
  24. </p>
  25. ## Overview
  26. `mcp-kit` turns the repetitive setup around an MCP application into a short, guided workflow. Choose what you are building, select a language and transport, then decide how much engineering infrastructure you want. The CLI writes a working project that follows the same choices all the way through its source, scripts, tests, and documentation.
  27. It is designed for both sides of an MCP integration:
  28. | Project | What the generated starter provides |
  29. | -------------- | ---------------------------------------------------------------------------------------------------------------- |
  30. | **MCP Server** | A structured server with tools, resources, prompts, lifecycle handling, and the transports you selected |
  31. | **MCP Client** | A client with connection helpers and an end-to-end example that discovers and uses tools, resources, and prompts |
  32. ## Why mcp-kit?
  33. - **Start with a real MCP workflow** — generated starters include working protocol primitives and a small knowledge-base example, not an empty entry file.
  34. - **Build either side** — create a server or a client from the same CLI.
  35. - **Choose your runtime shape** — use TypeScript or JavaScript with STDIO, Streamable HTTP, or both.
  36. - **Keep only the tooling you need** — start with the recommended setup or select individual plugins.
  37. - **Develop immediately** — generated scripts cover local development, production builds, linting, testing, and coverage when enabled.
  38. - **Stay close to the protocol** — server templates separate tools, resources, prompts, and transports into focused modules.
  39. ## Quick start
  40. Run the CLI with your package manager:
  41. ```bash
  42. npm create mcp-kit@latest
  43. ```
  44. ```bash
  45. pnpm create mcp-kit
  46. ```
  47. ```bash
  48. yarn create mcp-kit
  49. ```
  50. `bun create mcp-kit` and `deno init --npm mcp-kit` are also supported.
  51. The interactive setup asks for:
  52. | Choice | Options |
  53. | ------------ | ------------------------------------------------------------------------------------------------------- |
  54. | Project type | MCP Server · MCP Client |
  55. | Language | TypeScript · JavaScript |
  56. | Transport | STDIO · Streamable HTTP · both |
  57. | Template | Standard · Custom |
  58. | Plugins | GitHub Actions · Vitest · MCP Inspector (server) · ESLint/Prettier/Lint-staged · Commitlint · Changelog |
  59. | Dependencies | Install now · install later |
  60. After generation:
  61. ```bash
  62. cd mcp-server-starter
  63. npm run dev
  64. ```
  65. ## What gets generated
  66. The exact output follows your answers. A TypeScript server with both transports uses a structure like this:
  67. ```text
  68. src/
  69. ├── data/ # Example knowledge-base data
  70. ├── prompts/ # User-controlled prompt templates
  71. ├── resources/ # Application-controlled context
  72. ├── services/
  73. │ ├── stdio.ts # Local process transport
  74. │ └── web.ts # Streamable HTTP transport
  75. ├── tools/ # Model-controlled actions
  76. ├── types/
  77. ├── utils/
  78. └── index.ts # CLI entry point
  79. ```
  80. Depending on the selected plugins, the project can also include Vitest, GitHub Actions, MCP Inspector, lint and formatting rules, Git hooks, commit checks, and changelog tooling.
  81. ## Server starter
  82. The server template demonstrates how the three MCP primitives work together:
  83. 1. `search_documents` searches the starter knowledge base and returns structured results with stable resource URIs.
  84. 2. `kb://documents/{documentId}` exposes the matching document as an MCP resource.
  85. 3. `review_document` packages that resource into a reusable review prompt.
  86. The same server can be generated for local STDIO integrations, a Streamable HTTP endpoint at `/mcp`, or both.
  87. Common development commands:
  88. ```bash
  89. npm run dev # start the default development transport
  90. npm run dev:stdio # start the STDIO server, when selected
  91. npm run dev:web # start the Streamable HTTP server, when selected
  92. npm run build
  93. ```
  94. ## Client starter
  95. The client template includes transport-specific connection helpers and an end-to-end demo that:
  96. - negotiates the protocol version;
  97. - lists tools, resources, and prompts;
  98. - calls `search_documents`;
  99. - reads the returned resource URI;
  100. - retrieves the `review_document` prompt;
  101. - closes the client connection cleanly.
  102. Use it as a runnable reference or as the base for your own MCP host integration.
  103. ## Standard or custom setup
  104. The **Standard** template is the fast path. It enables GitHub Actions, Vitest, code-quality tooling, commit checks, changelog support, and MCP Inspector for server projects.
  105. Choose **Custom** when you want a smaller starter and select only the plugins that belong in your workflow.
  106. ## Documentation
  107. - [What is MCP Kit?](https://my-mcp-hub.github.io/mcp-kit/guide/what-is-mcp-kit)
  108. - [Getting started](https://my-mcp-hub.github.io/mcp-kit/guide/getting-started)
  109. - [What is MCP?](https://my-mcp-hub.github.io/mcp-kit/guide/what-is-mcp)
  110. ## Contributing
  111. Contributions and bug reports are welcome. [Open an issue](https://github.com/my-mcp-hub/mcp-kit/issues/new/choose) or submit a pull request, and follow the project [Code of Conduct](./CODE_OF_CONDUCT.md).
  112. ### Contributors
  113. <a href="https://github.com/my-mcp-hub/mcp-kit/graphs/contributors">
  114. <img src="https://contrib.rocks/image?repo=my-mcp-hub/mcp-kit" alt="mcp-kit contributors" />
  115. </a>
  116. ## License
  117. [MIT](./LICENSE) © Michael Sun

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.