Skip to main content
Glama

Related Servers

Alternatives to AssetRAG

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to search and access open-source code, documentation, and package information via a local MCP server.
      2,658 npm
      130
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to search local repositories through hybrid keyword and embedding retrieval, read matched chunks, and list indexed repos via MCP, without API keys or cloud services.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to inspect files, search text, compare directories, read symbols, and apply structured edits against large codebases through bounded, local-first MCP tools.
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a local, multi-repo code graph for symbol exploration, blast radius analysis, co-change mining, and durable code-anchored memory via MCP tools.
      128 npm
      16
      Business Source 1.1

    TDQS

    B3.1/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tools pair a distinct resource with an action, but knowledge/rule retrieval is crowded: find_knowledge, search_lessons, get_rules, and get_knowledge all surface fixes, rules, or lessons, and search_assets adds another search entry point. The 'Call when' guidance and route_task reduce confusion, but an agent can still hesitate between find_knowledge and search_lessons when handling an error.

    Naming Consistency4/5

    The set is overwhelmingly snake_case with verb_noun names such as get_asset, check_license, import_asset, record_failure, and promote_failure_to_rule. The exceptions—library_stats, knowledge_stats, and repo_map—are readable, common noun-style names and do not break predictability.

    Tool Count3/5

    Eighteen tools is above the ideal 3–15 range and feels heavy for one server; several workflows consume multiple endpoints, including asset search/get/license/import/harvest and knowledge search/get/stats/save. The categories are coherent, but some consolidation could reduce surface area.

    Completeness4/5

    Coverage is broad: assets can be searched, inspected, license-checked, imported, and harvested, while knowledge, lessons, rules, failures, audits, and repo mapping all have entry points. Minor gaps remain around update/delete or resolving quarantined/conflicting knowledge, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues