mcp-to-skill_skill

This skill converts MCP servers into Claude Code Skills, generating complete packages with SKILL.md, scripts, and references for easy reuse.

Python

10

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill bahayonghang/my-claude-code-settings --skill mcp-to-skill

SKILL.md4.1 KB

Overview

This skill converts MCP (Model Context Protocol) servers into reusable Claude Code skills with a complete package, scripts, and reference docs. It supports TypeScript/JavaScript and Python MCP servers and automates mapping of tools, parameters, and dependencies into a skill layout. Use it to standardize, distribute, or analyze MCP codebases for reuse.

How this skill works

The converter scans the MCP project to extract entry points, tool implementations, dependencies, and runtime details. It maps each MCP tool to either an executable script or an instruction section, generates a skill manifest and scripts folder, and produces a reference document listing tools, parameters, and examples. The output includes startup scripts for server-backed tools, standalone tool scripts for simple actions, and a checklist to validate the final package.

When to use it

You have an MCP server codebase and want a reusable Claude Code skill package
You ask for “MCP to skill”, “convert MCP”, or similar phrases indicating conversion
You need to analyze MCP server structure to document tools and parameters
You want to distribute MCP tools as standalone scripts or instruction-based skill content
You prefer an automated mapping from MCP concepts to skill layout

Best practices

Scan package.json or pyproject.toml to capture dependencies and entry points before conversion
Prefer script-based generation for complex tool logic and instruction-based sections for simple utilities
Include explicit parameter definitions and concrete examples for every tool
Mark server-dependent tools clearly and provide a startup script and usage steps
Run and test generated scripts in the target runtime (node or python) before packaging

Example use cases

Convert a TypeScript MCP server into a skill with scripts for each tool and a startup script for server-backed endpoints
Extract standalone utilities from a Python MCP project and publish them as instruction-based skill entries
Audit an MCP repository to produce a catalog of tools, parameters, and dependency requirements for internal documentation
Create a hybrid skill where some tools run as local scripts and others require the MCP server to be started
Prepare a skill package that includes executable scripts, a manifest, and a references document for developer handoff

FAQ

The converter supports TypeScript/JavaScript and Python MCP servers. It detects entry points and tools in those ecosystems.

How are server-dependent tools handled?

Server-dependent tools are packaged with a startup script and clear instructions to run the MCP server before invoking tool endpoints; standalone tools are emitted as executable scripts or instruction text.