AssetRAG
Related Servers
Alternatives to AssetRAG
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents to map a codebase into declared documentation, actual code, and tests; inspect gaps and recommendations; store and search lasting knowledge; and manage local work items over MCP stdio.16MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT

GitHitsofficial
AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to search and access open-source code, documentation, and package information via a local MCP server.2,658 npm130Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to inspect files, search text, compare directories, read symbols, and apply structured edits against large codebases through bounded, local-first MCP tools.4Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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 npm16Business Source 1.1
TDQS
Scored across 18 tools
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.
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.
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.
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.