create-mcp

Create end-to-end MCP development workflows with TypeScript scaffolding and Smithery config generation.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/haomingkoo/create-mcp --skill create-mcp-haomingkoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-mcp
Source: https://github.com/haomingkoo/create-mcp/tree/main
Command: npx skills add https://github.com/haomingkoo/create-mcp --skill create-mcp-haomingkoo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code skills let you automate end-to-end MCP server creation and auditing, removing manual scaffolding and discovery friction.

Core Features & Use Cases

  • Auto-detect path (create from scratch or audit an existing server)
  • Scaffold TypeScript boilerplate that enforces all 10 Smithery dimensions
  • Audit existing MCPs, fix issues in one pass, and generate publish-ready artifacts
  • Generate Smithery config files (smithery.yaml or smithery.remote-config.json) and ready-to-publish metadata
  • Guide through tool naming with dot notation for optimal Smithery scoring

Quick Start

Restart Claude Code and run /create-mcp in any Claude session.

Frequently Asked Questions about create-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a TypeScript MCP server from scratch for Claude Code?

Scaffolding a TypeScript MCP server from scratch is handled by running the /create-mcp command, which generates boilerplate and enforces Smithery's 10 dimensions to produce a production-ready server.

How do I audit an existing MCP server to fix Smithery publishing issues?

Auditing an existing MCP server involves running the skill to auto-detect your current project, identify failures across Smithery's 10 dimensions, and fix issues in one pass to generate publish-ready artifacts.

What are the Smithery server metadata requirements for publishing an MCP?

Smithery server metadata requirements include proper dot-notation tool names, annotations, server instructions, and a valid smithery.yaml or smithery.remote-config.json file generated for optimal scoring.

Can I use this skill to generate a smithery.yaml configuration file?

Generating a smithery.yaml configuration file is supported by this skill, which outputs ready-to-publish artifacts including smithery config files and proper metadata required for server discovery.

Does the MCP scaffolding workflow enforce dot-notation for tool names?

The MCP scaffolding workflow enforces dot-notation for tool names, guiding you through the naming process to ensure optimal Smithery scoring and compliance with server metadata standards.