mcp-skill-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| skills_path | Yes | The path to the directory containing your skill folders (each containing a SKILL.md and scripts). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsB | List all available skills |
| get_skillA | Get skill details including commands and parameters |
| run_skillC | Execute a skill command with parameters |
| refresh_skillsA | Refresh the skill list (use after adding new skills) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: listing, retrieving details, executing, and refreshing. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (list_skills, get_skill, run_skill, refresh_skills), making the API predictable.
Four tools is a tight, well-scoped set for a skill management server, with each tool covering a clear and necessary operation.
The surface covers the full expected lifecycle: discover skills, inspect skill details, execute skills, and refresh the catalog. No obvious gaps for this domain.