Progressive Skills MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLS_SOURCE | Yes | Path to the directory containing skills. Must be a valid existing directory. Examples: /home/username/skills, C:\Users\YourName\skills, /app/skills |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_resourceA | [FALLBACK ONLY] Fetch a skill resource by URI. IMPORTANT: Only use this if your client does NOT support native MCP resource fetching. If your client supports MCP resources, use the native resource fetching mechanism instead. This tool only supports URIs in the format: resource://skillz/{skill-slug}/{path}. Resource URIs are provided in skill tool responses under the 'resources' field. |
| load_skillA | Load the complete instructions for a skill. Use this when you've decided a skill is relevant based on the skill metadata in your system prompt. Returns the full SKILL.md content without frontmatter. |
| read_skill_fileA | Read a specific file from a skill's directory. Use this when skill instructions reference a file (e.g., 'See references/api_reference.md'). Provide the skill name and relative file path. |
| list_skill_filesA | List files available in a skill's directory. Use this to discover what reference files, scripts, or resources a skill provides. Optionally specify a subdirectory like 'references' or 'scripts'. |
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 action: loading the main skill, reading a specific file, listing files, and fetching resources as a fallback. The purposes are clearly separated with specific use-case guidance, so an agent can reliably choose the right one.
All tools follow a consistent verb_noun pattern (fetch_resource, load_skill, read_skill_file, list_skill_files) with no mixed conventions or vague verbs. The naming is predictable and matches the operation performed.
Four tools is well-scoped for a skill management server: loading, reading, listing, and fetching resources. Each tool earns its place without redundancy, and the count is neither sparse nor excessive for the domain.
The set covers the core operations needed to interact with skills (load, read, list, fetch). The only potential gap is the absence of a dedicated 'list all skills' tool, but skills are advertised in the system prompt, so this is a minor gap that agents can work around.