Shared Skills Registry MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSR_MCP_URL | Yes | URL of the local Shared Skills Registry HTTP service | |
| SSR_MCP_SKILLS_ROOT | Yes | Local root directory where skills will be installed |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_shared_skillsD | List Shared Skills Registry metadata. |
| describe_shared_skillC | Describe one Shared Skills Registry skill entry. |
| search_shared_skillsC | Search Shared Skills Registry metadata. |
| retrieve_shared_skillC | Retrieve a checksum-bearing Shared Skills Registry source bundle. |
| install_shared_skillC | Install a shared skill into a configured local skills directory. |
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 5 tools
Each tool targets a distinct operation: describing an entry, installing, listing metadata, retrieving source bundles, and searching. There is no overlap in functionality, and the descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_shared_skills, retrieve_shared_skill). This uniformity makes the set predictable for an agent.
With 5 tools, the collection is well-scoped for a shared skills registry. Each tool covers a core operation without unnecessary bloat or feeling incomplete.
The tool set covers discovery (search, list), details (describe), acquisition (retrieve), and installation (install). Missing operations like uninstall or update are not critical for a read-oriented registry, so the surface is largely complete for its purpose.