MCP server
by fkesheh
Skill Management is workflow automation software that builds, organizes, and executes maintainable software workflows wi
Manages reusable automation scripts with metadata, environment variables, and dependency handling in a structured ~/.skill-mcp/skills directory. Enables unified execution of Python code that combines multiple skills in a single run.
Skill Management is a community-built MCP server published by fkesheh that provides AI assistants with tools and capabilities via the Model Context Protocol. Skill Management is workflow automation software that builds, organizes, and executes maintainable software workflows wi It is categorized under developer tools. This server exposes 9 tools that AI clients can invoke during conversations and coding sessions.
You can install Skill Management in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Skill Management is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Skill Management has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Skill Management reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
According to our notes, Skill Management benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Skill Management into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: Skill Management surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Skill Management is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend Skill Management for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated Skill Management against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Skill Management surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Skill Management reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 73
A Model Context Protocol (MCP) server that enables Claude to manage skills stored in ~/.skill-mcp/skills. This system allows Claude to create, edit, run, and manage skills programmatically, including execution of skill scripts with environment variables.
Status: ✅ Production Ready Test Coverage: 86% (145/145 tests passing) Deployed: October 18, 2025 Architecture: 22-module modular Python package with unified CRUD architecture
TL;DR: Write Python code that unifies multiple skills in one execution - follows Anthropic's MCP pattern for 98.7% more efficient agents.
This project consists of two main components:
src/skill_mcp/server.py) - A Python package providing 5 unified CRUD tools for skill management~/.skill-mcp/skills/) - Where you store and manage your skillsBuild once, compose everywhere - Execute Python code that seamlessly combines multiple skills in a single run:
# One execution, multiple skills unified!
# Imports from calculator, data-processor, and weather skills
from math_utils import calculate_average # calculator skill
from json_fetcher import fetch_json # data-processor skill
from weather_api import get_forecast # weather skill
# Fetch weather data
weather = fetch_json('https://api.weather.com/cities')
# Calculate averages using calculator utilities
temps = [city['temp'] for city in weather['cities']]
avg_temp = calculate_average(temps)
# Get detailed forecast
forecast = get_forecast('London')
print(f"Average temperature: {avg_temp}°F")
print(f"London forecast: {forecast}")
What makes this powerful:
Efficiency gains:
This aligns with Anthropic's research showing agents scale better by writing code to call tools rather than making direct tool calls for each operation.
Unlike the Claude interface, this system uses the Model Context Protocol (MCP), which is:
Your skills can run in:
Instead of manually copying, zipping, and uploading files:
❌ OLD WAY: Manual process
1. Create skill files locally
2. Zip the skill folder
3. Upload to Claude interface
4. Wait for processing
5. Can't easily modify or version
✅ NEW WAY: LLM-managed programmatically
1. Tell Claude: "Create a new skill called 'data-processor'"
2. Claude creates the skill directory and SKILL.md
3. Tell Claude: "Add a Python script to process CSVs"
4. Claude creates and tests the script
5. Tell Claude: "Set the API key for this skill"
6. Claude updates the .env file
7. Tell Claude: "Run the script with this data"
8. Claude executes it and shows results - all instantly!
Key Benefits:
.env files~/.skill-mcp/
└── skills/ # Your skills directory
├── example-skill/
│ ├── SKILL.md # Required: skill definition
│ ├── .env # Optional: skill-specific environment variables
│ ├── scripts/ # Optional: executable scripts
│ ├── references/ # Optional: documentation
│ └── assets/ # Optional: templates, files
└── another-skill/
├── SKILL.md
└── .env
Note: The MCP server is installed via uvx from PyPI and runs automatically. No local server file needed!
This project uses uv for fast, reliable Python package management.
# Install uv (includes uvx)
curl -LsSf https://astral.sh/uv/install.sh | sh
Add the MCP server to your configuration. The server will be automatically downloaded and run via uvx from PyPI.
Claude Desktop - Edit the config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonCursor - Edit the config file:
~/.cursor/mcp.json%USERPROFILE%\.cursor\mcp.json~/.cursor/mcp.json{
"mcpServers": {
"skill-mcp": {
"command": "uvx",
"args": [
"--from",
"skill-mcp",
"skill-mcp-server"
]
}
}
}
That's it! No installation needed - uvx will automatically download and run the latest version from PyPI.
Restart Claude Desktop or Cursor to load the MCP server.
In a new conversation:
List all available skills
Claude should use the skill-mcp tools to show skills in ~/.skill-mcp/skills/.
For development in this repository:
uv sync # Install/update dependencies
uv run python script.py # Run Python with project environment
uv add package-name # Add a new dependency
uv pip list # Show installed packages
uv run pytest tests/ -v # Run tests
Note: uv automatically creates and manages .venv/ - no need to manually create virtual environments!
✅ BOTH run_skill_script AND execute_python_code support PEP 723!
Python scripts and code can declare their own dependencies using uv's inline metadata. The server automatically detects this and uses uv run to handle dependencies:
#!/usr/bin/env python3
# /// script
# dependencies = [
# "requests>=2.31.0",
# "pandas>=2.0.0",
# ]
# ///
import requests
import pandas as pd
# Your script code here - dependencies are automatically installed!
response = requests.get("https://api.example.com/data")
df = pd.DataFrame(response.json())
print(df.head())
Benefits:
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.