npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

create-mcp-kit

v1.0.1

Published

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

Readme

Create-MCP-Kit

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

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 transport modes:

  1. STDIO: Communication through standard input/output streams
  2. Streamable HTTP: RESTful API with streaming capabilities
  3. SSE (Server-Sent Events): Real-time event streaming from server to client

MCP Tools

Implement custom tools that can be used by MCP clients:

// Full implementation example
import { z } from 'zod'
import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js'

export default function register(server, options) {
  server.registerTool(
    'GetData',
    {
      title: 'Get Data',
      description: 'Get Data',
      inputSchema: {
        keyword: z.string().describe('search keyword'),
      },
    },
    async ({ keyword }) => {
      const { success, data, message } = await getData(keyword, options)
      return {
        content: [
          {
            type: 'text',
            text: success ? data : message,
          },
        ],
      }
    },
  )
}

export const getData = async (keyword, options) => {
  if (!keyword || keyword === 'error') {
    return {
      success: false,
      message: 'Invalid keyword',
    }
  }

  return {
    success: true,
    data: `Data for ${keyword}`,
  }
}

MCP Resources

Define resources that can be accessed by MCP clients:

// Full implementation example
import { type McpServer, ResourceTemplate } from '@modelcontextprotocol/sdk/server/mcp.js'
import type { OptionsType } from '@/types'

export const registerResources = (server: McpServer, options: OptionsType) => {
  server.registerResource(
    'search',
    new ResourceTemplate('search://{keyword}', {
      list: undefined,
    }),
    {
      title: 'Search Resource',
      description: 'Dynamic generate search resource',
    },
    async (uri, { keyword }) => {
      return {
        contents: [
          {
            uri: uri.href,
            text: `search ${keyword}`,
          },
        ],
      }
    },
  )
}

MCP Prompts

Create reusable prompts for MCP clients:

// Full implementation example
import { z } from 'zod'
import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js'

export const registerPrompts = (server: McpServer) => {
  server.registerPrompt(
    'echo',
    {
      title: 'Echo Prompt',
      description: 'Creates a prompt to process a message.',
      argsSchema: {
        message: z.string(),
      },
    },
    ({ message }) => {
      return {
        messages: [
          {
            role: 'user',
            content: {
              type: 'text',
              text: `Please process this message: ${message}`,
            },
          },
        ],
      }
    },
  )
}

MCP Client Features

Multiple Transport Modes

Connect to MCP servers using different transport modes:

// Import the MCP client
import { McpClient } from '@modelcontextprotocol/sdk/client/mcp.js'
import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/transports/stdio.js'
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/transports/streamable-http.js'
import { SSEClientTransport } from '@modelcontextprotocol/sdk/client/transports/sse.js'

// Create a new MCP client
const client = new McpClient()

// STDIO Transport
const stdioClientTransport = new StdioClientTransport({
  command: 'npx',
  args: ['-y', '@my-mcp-hub/node-mcp-server'],
  env: process.env,
})
await client.connect(stdioClientTransport)

// Streamable HTTP Transport
const streamableBaseUrl = new URL('http://localhost:8401/mcp')
const streamableClientTransport = new StreamableHTTPClientTransport(streamableBaseUrl)
await client.connect(streamableClientTransport)

// SSE Transport
const sseBaseUrl = new URL('http://localhost:8401/sse')
const sseClientTransport = new SSEClientTransport(sseBaseUrl)
await client.connect(sseClientTransport)

Tool Calling

Call tools provided by MCP servers:

// List available tools
const tools = await client.listTools()
console.log(tools)

// Call a tool
const callResult = await client.callTool({
  name: 'GetData',
  arguments: {
    keyword: 'Hello',
  },
})
console.log(callResult.content)

Resource Access

Access resources provided by MCP servers:

// List available resources
const resources = await client.listResources()
console.log(resources)

// Get a resource
const resource = await client.getResource('search://example')
console.log(resource.contents)

Prompt Usage

Use prompts provided by MCP servers:

// List available prompts
const prompts = await client.listPrompts()
console.log(prompts)

// Use a prompt
const prompt = await client.getPrompt('echo', { message: 'Hello, world!' })
console.log(prompt.messages)

Contributing

Feel free to dive in! Open an issue or submit PRs.

Standard Readme follows the Contributor Covenant Code of Conduct.

Contributors

This project exists thanks to all the people who contribute.

License

MIT © MichaelSun