skillsmp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLSMP_API_KEY | Yes | Your SkillsMP API key. Required to authenticate requests to skillsmp.com. Obtain one by registering at https://skillsmp.com. |
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 |
|---|---|
| search_skillsmpA | Searches the SkillsMP marketplace for agent skills, workflows, and prompts using keywords. Args: q: The search query or keyword (e.g., 'automation', 'SEO', 'react'). limit: Number of results to return (default: 20, max: 100). sortBy: Sort order of the results ("stars" or "recent"). category: Optional slug to filter by category (e.g., 'data-ai', 'devops'). language: ISO code to filter by skill content language (e.g., 'en', 'zh'). |
| fetch_skillsmp_skillA | Fetches the full SKILL.md markdown content for a skill using its githubUrl returned from search. Args: githubUrl: The githubUrl of the skill returned from search_skillsmp. |
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 2 tools
search_skillsmp is the discovery entry point, while fetch_skillsmp_skill retrieves a specific skill's markdown content using a githubUrl. Their inputs, outputs, and purposes are clearly distinct with no realistic overlap.
Both tools use snake_case action-prefixed names, making the pattern mostly predictable. The minor inconsistency is that search_skillsmp names the marketplace while fetch_skillsmp_skill explicitly names the skill object.
Two tools is borderline thin, but it is understandable for a narrow search-then-fetch marketplace lookup server. There are no separate management or browsing tools, so the count feels slightly under-scoped rather than bloated.
Search claims to cover skills, workflows, and prompts, but only skills have a fetch operation for their content. This leaves workflows and prompts as dead ends after search results are returned, which is a significant gap relative to the stated marketplace scope.