claude-skills-mcp
Related Servers
Alternatives to claude-skills-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP (Model Context Protocol) Server for skill4agent - Search, view, and install AI skills in AI conversations.310 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMCP Memory Server for Claude Code that provides persistent context across sessions using semantic search (RAG).Apache 2.0
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables Claude Desktop or Claude Code to ingest and search local documents using vector embeddings, returning relevant chunks as tool results for the model to reason over.-
- AlicenseNot gradedqualityDmaintenanceA universal MCP server that enables any MCP-compatible agent to use Anthropic's Claude Agent Skills with progressive disclosure, reducing context overhead while maximizing capability.47Apache 2.0
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that provides semantic search (RAG) over code repositories, enabling AI clients like Claude and Gemini to access project context without manual re-upload.-
- AlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that transforms Claude-style skills and resources into callable tools for any MCP-compatible agent or client. It automatically discovers, exposes, and executes scripts from skills organized in local directories or packaged archives.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_skills provides an inventory, search_skills performs semantic search for task relevance, and read_skill_document retrieves specific documents. The descriptions explicitly differentiate them, with list_skills even noting to use search_skills for task-specific needs, eliminating overlap.
All tools follow a consistent verb_noun pattern with snake_case: list_skills, search_skills, and read_skill_document. This uniformity makes the set predictable and easy to understand, enhancing usability for agents.
With 3 tools, the count is reasonable for a skills management server, covering exploration, search, and document retrieval. It feels slightly thin but well-scoped for its purpose, as each tool serves a distinct workflow without unnecessary bloat.
The tool surface covers core workflows: inventory listing, semantic search, and document access. Minor gaps exist, such as no direct skill execution or management tools (e.g., load/unload), but agents can work around this by using retrieved documents, making it nearly complete for the domain.