Skip to main content
Glama

Related Servers

Alternatives to skill-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Serves any directory of Agent Skills (SKILL.md folders) over MCP, exposing skills/list, skills/get, and skill:// resources so clients can enumerate and retrieve each skill's frontmatter and files. Every returned file comes with a real SHA-256 digest, letting clients verify content rather than merely trust it.
      15 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Serves Agent Skills—folders with a SKILL.md and optional references, scripts, and assets—to any MCP client, exposing read-only tools to list, retrieve, and inspect skills and their bundled files. Ships with an XSLT hardening skill and can also serve private local skill folders via configuration.
      4
      760 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.
      3
      29 PyPI
      30
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to discover and load agent skills by name over MCP from commit-pinned Git repositories, returning skill instructions and supporting files only on demand so nothing is preloaded into context.
      40 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turns any folder of Markdown agent skills into a local MCP server, exposing them as tools, prompts, and resources for MCP-compatible clients.
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct stage of the skill lifecycle: listing skills, loading a SKILL.md, reading bundled files, and executing declared scripts. There is no overlap—file reading and script execution are clearly separated, and descriptions reinforce the boundaries.

    Naming Consistency5/5

    All four tools use a uniform skill_<verb> pattern (skill_list, skill_load, skill_file, skill_run). The convention is predictable and readable throughout.

    Tool Count5/5

    Four tools is well-scoped for a skill-discovery and execution server. Each tool earns its place with no redundant or filler operations.

    Completeness5/5

    The surface covers the full lifecycle: enumerate skills, load instructions, read bundled files, and run declared scripts, with clear guidance on chaining (e.g. read files after load). No obvious gaps or dead ends for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data