Skip to main content
Glama

Skill MCP Server šŸš€

šŸ“– What is Skill MCP Server?

Skill MCP Server is a standard Model Context Protocol (MCP) server that bridges Claude Skills to any AI agent that supports MCP.

Previously, Claude Skills were mainly used in Anthropic's official tools. If your AI application doesn't support Skills, you'd have to implement your own parsing and execution logic, which is a hassle. With this project, you can simply configure it and let any MCP-compatible Agent use standard Skill files directly.


Related MCP server: skills-master-mcp

šŸŽ¬ Demo

šŸ’” Core Concepts

  • šŸ”Œ MCP (Model Context Protocol): Think of it as a "USB interface" for AI. As long as your AI assistant supports this interface, it can connect to various tools and services.

  • šŸ“¦ Claude Skills: Think of them as "skill packages" for AI. They're not just documentation — they include instructions (SKILL.md), accompanying scripts (Python/JS), and reference materials.

Skill MCP Server is a "converter" that helps various agents use the Skill ecosystem, enabling plug-and-play functionality.

🌟 Why Choose Skill MCP Server?

If your Agent doesn't support Skills yet, this project can help you quickly integrate:

Dimension

Natively Supported Agents (e.g., Claude Code)

Other Agents (with this project)

Access Barrier

Deep integration, usually non-portable

Low barrier, standard MCP protocol

Development Burden

Official implementation complete

Zero code, no need to build Skill parser

Flexibility

Tied to specific clients

Cross-platform, works with any MCP-compatible agent

Feature Parity

Full script, resource & file stream support

Perfect alignment, same dynamic execution & resource access

✨ Features

  • šŸ› ļø Highly Standardized: Strictly follows MCP protocol

  • šŸŒ Universal Compatibility: Not tied to any vendor, works with all MCP-compatible AI clients

  • ⚔ Zero-Code Integration: Helps agents without native Skill support quickly access the Skill ecosystem

  • šŸ“¦ Fully Compatible: Supports SKILL.md format and scripts/, references/ resource directories

  • šŸ“‚ Workspace Isolation: Supports --workspace parameter to specify where Skill output files are stored

  • šŸ”„ Hot Reload: Add new skills without restarting the server

  • šŸ”’ Secure by Design: Path validation, sandboxed file operations

šŸš€ Quick Start

Recommended: Use uvx to run without manual installation.

šŸ“„ Installation

# Using pip
pip install skill-mcp-server

# Using uv (recommended)
uv pip install skill-mcp-server

āš™ļø Configure MCP

Add Skill MCP Server to your MCP client configuration. All MCP-compatible clients use the same configuration format:

Using uvx (recommended, no installation needed):

{
  "mcpServers": {
    "skill-server": {
      "command": "uvx",
      "args": [
        "skill-mcp-server",
        "--skills-dir", "/path/to/your/skills",
        "--workspace", "/path/to/workspace"
      ]
    }
  }
}

Using local installation:

{
  "mcpServers": {
    "skill-server": {
      "command": "python",
      "args": [
        "-m", "skill_mcp_server",
        "--skills-dir", "/path/to/your/skills",
        "--workspace", "/path/to/workspace"
      ]
    }
  }
}

Configuration file locations:

  • Claude Desktop: claude_desktop_config.json (location varies by OS)

  • Claude Code: ~/.claude.json

  • Other MCP clients: Refer to your client's documentation

Parameter Explanation:

  • --skills-dir: Core parameter. Set to the root directory containing all Skill folders you want your agent to use.

  • --workspace: Important parameter. Specifies where Skill execution output files (code, reports, etc.) are saved.

šŸ› ļø Available Tools (MCP Tools)

Once connected, your AI agent can use the following tools:

  1. šŸ” list_skills: List all available skills

  2. šŸ“š skill: Load a specific skill to get detailed instructions from its SKILL.md

  3. šŸ“„ skill_resource: Read reference documents or templates from skill packages

  4. ā–¶ļø skill_script: Execute scripts bundled with skills in a secure environment

  5. šŸ“– file_read: Read files from the specified workspace

  6. āœļø file_write: Write files to the specified workspace

  7. āœļø file_edit: Edit existing files in the workspace

šŸ“ Creating Skills

A standard Skill structure looks like this:

my-skills/
└── deploy-helper/           # Skill folder
    ā”œā”€ā”€ SKILL.md             # Core documentation (required)
    ā”œā”€ā”€ scripts/             # Executable scripts
    └── references/          # Reference materials

SKILL.md Example:

---
name: deploy-helper
description: Help users deploy applications to production with one click
---

# Deploy Helper Usage Guide

When users request deployment, follow these steps:
1. Use `skill_resource` to read the deployment template.
2. Modify local configuration files.
3. Call `skill_script` to execute the deployment script.

SKILL.md Format

---
name: my-skill
description: Brief description of what this skill does and when to use it
---

# My Skill

## Overview

Explain what this skill enables the AI to do.

## Usage

Step-by-step instructions for the AI agent...

## Available Resources

- `scripts/process_data.py` - Process input data
- `assets/report_template.md` - Output template

šŸ’¼ Use Cases

  • šŸ“Š Data Analysis: Enable agents to perform data analysis

  • šŸ“ Document Generation: Enable agents to create professional documents

  • šŸ”— API Integration: Enable agents to integrate with specific APIs

  • šŸ” Code Review: Enable agents to follow team standards

  • šŸš€ DevOps Tasks: Enable agents to automate deployment workflows

šŸ“š Documentation

šŸ› ļø Development

# Clone the repository
git clone https://github.com/ephemeraldew/skill_mcp.git
cd skill_mcp

# Install development dependencies
uv pip install -e ".[dev]"

# Run tests
pytest

# Run linting
ruff check src/

šŸ¤ Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

If this project helps you, please give it a ā­ļø Star.

šŸ“„ License

MIT License - see LICENSE for details.


Available Tools

7 tools
file_editB

Edit an existing file in the workspace using search and replace. The old_string must exist in the file and should be unique.

Inputs: file_path (required), old_string (required), new_string (required), replace_all.

file_readB

Read a file from the workspace directory. Use this tool to read files generated by skills or modified by the user.

Inputs: file_path (required).

file_writeA

Create or overwrite a file in the workspace. Use this tool when a skill needs to generate output files.

Inputs: file_path (required), content (required).

list_skillsA

List all available skills with their names and descriptions. Use this to discover what skills are available before loading one.

Inputs: no named parameters.

skillC

Load a skill to get detailed instructions for a specific task. No skills are currently available.

Inputs: name (required).

skill_resourceA

Read a resource file from a skill's directory. Use this tool after loading a skill to read referenced files like templates, examples, or reference documentation. The resource_path should be relative to the skill's base directory (e.g., 'assets/template.md', 'references/api_reference.md').

Inputs: skill_name (required), resource_path (required).

skill_scriptB

Execute a script from a skill's scripts/ directory. Use this tool to run Python (.py), Shell (.sh/.bash), JavaScript (.js), or TypeScript (.ts) scripts bundled with a skill. Scripts are executed in the workspace directory.

Inputs: skill_name (required), script_path (required), args.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: file operations (edit/read/write) are separate from skill operations (list/load/resource/script). The descriptions reinforce unique functions, such as file_edit for search-and-replace versus file_write for creation/overwriting, and skill_script for execution versus skill_resource for reading files. An agent can easily differentiate between tools based on their specific actions and contexts.

    Naming Consistency5/5

    All tools follow a consistent snake_case naming pattern with clear verb_noun structures: file_edit, file_read, file_write, list_skills, skill, skill_resource, and skill_script. The naming is predictable, using prefixes like 'file_' and 'skill_' to group related tools, making it easy for agents to understand relationships and purposes without confusion or deviation.

    Tool Count5/5

    With 7 tools, the count is well-scoped for the server's purpose of managing files and skills. It covers essential operations like file CRUD (edit/read/write) and skill lifecycle (list/load/resource/script), providing a balanced set without being too sparse or overwhelming. Each tool earns its place by addressing a core need in the domain, avoiding redundancy or gaps.

    Completeness4/5

    The tool surface is nearly complete for the domain of file and skill management, covering key operations like file editing, reading, writing, skill listing, loading, resource access, and script execution. A minor gap exists in file operations, such as the lack of a delete_file tool, but agents can work around this by using file_write to overwrite or clear files. Overall, it supports core workflows effectively with no dead ends.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to dynamically discover and execute tools through a structured skills system. Serves as a documentation hub where skills are defined in directories, allowing progressive loading and interpretation of capabilities.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Connects AI coding agents to the SkillsMP marketplace, allowing users to search, read, and install over 8,000 community-made skills. It enables agents to gain new capabilities either through on-the-spot instruction or permanent installation without requiring an API key.
      5
      44 npm
      10
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A unified skill management and distribution hub that aggregates local skill folders and exposes them via MCP protocol to AI platforms, featuring lazy loading and hot reloading.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and retrieve over 89K skills on-demand at runtime, eliminating the need to manually install skills upfront.
      136
      MIT