Skip to main content
Glama

Related Servers

Alternatives to skill-router-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to install compatible SKILL.md skills from Git repositories or local directories into a persistent registry, then discover them through search, progressive loading, and asset reads. It exposes only user-selected hot skills as individual activation tools, keeping execution and trust decisions under explicit operator control.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search, recommend, and validate a stack of reusable skills from a local catalog, producing deterministic plans without modifying the project.
      6,708 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Indexes every skill across all installed plugins and enables the agent to find them instantly via BM25 search through an MCP tool.
      4 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to dynamically discover and execute tools through a structured skills system. Serves as a documentation hub where skills are defined in directories, allowing progressive loading and interpretation of capabilities.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to semantically search and retrieve relevant skills from a local Markdown skill database, reducing context waste by loading only needed skills through tiered detail levels and tool calls.
      16 npm
      6
      MIT

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation3/5

    Tools are mostly distinct in purpose: inventory summarizes the index, search finds candidates, recommend provides ranked suggestions, and explain returns metadata. However, search_skills and recommend_skills overlap notably in that both surface candidate skills for a task, with the difference (scored candidates vs. categorized recommendations) subtle enough that an agent could misselect. inventory_skills and explain_skill also both touch metadata/duplicate info.

    Naming Consistency4/5

    All four tools follow a consistent verb_noun pattern (inventory, search, recommend, explain) that is clear and readable. The verbs are varied but each communicates a distinct action well, and the noun 'skills' is consistent. Minor inconsistency: 'inventory' as a verb is slightly unconventional vs. the more standard 'list', but the pattern remains coherent.

    Tool Count4/5

    Four tools is a reasonable, focused count for a skill-routing server whose purpose is discovery/indexing/advisory. Each tool earns its place covering distinct stages of the workflow. Could arguably be slightly slim, but it's well-scoped and not overly heavy.

    Completeness3/5

    The surface covers indexing, searching, recommending, and explaining skills, which covers the core discovery workflow well. However, there's no tool for skill management operations (e.g., installing, removing, or updating skills), and no filter-by-category listing tool—gaps that agents might hit when they need to act on skills rather than just discover them. Still, for a routing/advisory purpose the surface is largely complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues