mcp-kit
Health Gecti
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Community trust — 97 GitHub stars
Code Basarisiz
- process.env — Environment variable access in docs/.vitepress/config.ts
- Hardcoded secret — Potential hardcoded credential in docs/.vitepress/config.ts
Permissions Gecti
- Permissions — No dangerous permissions requested
This is a command-line interface (CLI) scaffolding tool designed to quickly generate boilerplate projects for building Model Context Protocol (MCP) servers and clients. It provides developers with an easy starting point including TypeScript support, multiple transport modes, and development scripts.
Security Assessment
Overall Risk: Medium. While the core CLI functions safely without executing dangerous shell commands or requesting broad system permissions, the repository failed a critical code scan. A hardcoded credential or secret was detected inside the documentation configuration file (`docs/.vitepress/config.ts`). Additionally, this same file accesses environment variables via `process.env`. Because the actual secret is injected directly into the codebase rather than referenced safely, it poses a security risk. The project does not inherently access local sensitive data or make suspicious network requests, but the presence of hardcoded credentials is a significant vulnerability that indicates poor secret management practices.
Quality Assessment
The project is in excellent health and shows strong signs of active maintenance, with its most recent push occurring just today. It is properly licensed under the permissive and standard MIT license. Furthermore, it enjoys a good level of community trust and interest, currently backed by 97 GitHub stars. The generated boilerplate includes robust modern development tooling like ESLint, Prettier, and Vitest, indicating a high standard of code quality for the end user.
Verdict
Use with caution — the tool itself is a safe and active scaffolding utility, but developers should be wary of the project's poor secret management practices and ensure no sensitive data is accidentally committed to their newly generated projects.
A CLI tool to create MCP (Model Context Protocol) applications with ease.
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 modenpm run dev:web- Start the development server in web modenpm run build- Build the projectnpm 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 modenpm run build- Build the projectnpm 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:
- STDIO: Communication through standard input/output streams
- Streamable HTTP: RESTful API with streaming capabilities
- 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
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi