skillsmp-mcp
Related Servers
Alternatives to skillsmp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConnects AI coding agents to the SkillsMP marketplace, allowing users to search, read, and install over 8,000 community-made skills. It enables agents to gain new capabilities either through on-the-spot instruction or permanent installation without requiring an API key.512 npm10MIT
- AlicenseAqualityDmaintenanceConnects AI coding agents to the SkillFlow marketplace to search, discover, and retrieve detailed information about agent skills. It enables users to browse trending skills, categories, and publisher data directly through MCP-compatible environments.527 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to autonomously search, evaluate, and install skills from the skills.sh catalog.2413 npmISC
- AlicenseAqualityBmaintenanceLets AI agents search and discover skill files from a curated catalog to fill missing capabilities, providing download URLs for free items and purchase info for paid ones.31MIT
- AlicenseNot gradedqualityAmaintenanceEnables searching and retrieving details of 41,000+ agent skills, MCP servers, Claude Code plugins, and agentic loops from any MCP-capable agent.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search and retrieve over 89K skills on-demand at runtime, eliminating the need to manually install skills upfront.125MIT
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.