rag-rat
Related Servers
Alternatives to rag-rat
- AlicenseAqualityBmaintenanceGraph-based tool retrieval for LLM agents. Builds a tool graph from OpenAPI/MCP specs and retrieves multi-step workflows via hybrid search (BM25 + graph traversal + embedding), recovering accuracy from 12% to 82% with 79% fewer tokens. Also works as an MCP Proxy to aggregate multiple servers behind 3 meta-tools.691 PyPI17MIT
- AlicenseAqualityAmaintenanceProvides AI coding agents with five intelligence layers (dependency graph, git history, documentation, architectural decisions, code health) via nine MCP tools, enabling deep codebase understanding and reducing exploration cost.104,838 PyPI7,138AGPL 3.0
Related Servers
- AlicenseCqualityBmaintenanceLocal-first codebase intelligence engine providing AI coding agents with a typed MCP toolset for understanding and navigating code repositories.10052Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLocal-first repository memory for AI coding agents that indexes codebases into SQLite and exposes it through MCP tools, with a browser dashboard for architecture inspection.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceOffline-first, persistent repository memory for coding agents. Provides MCP tools for repository scanning, searching, context, and impact analysis, helping agents navigate and edit code efficiently.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP-style code memory for research repositories: enables file search, Python symbol extraction, import graph, and repo context packs.MIT
- AlicenseBqualityCmaintenanceIndexes a Python/JS/TS repository into a local SQLite knowledge graph so agents can trace callers, callees, imports, subclasses and covering tests, measure impact radius, rank diff risk, and summarize architecture without grepping files. Exposes these queries as MCP tools alongside an equivalent CLI, with no daemon, embeddings, or network access.10MIT
- 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.143 npm14Business Source 1.1
TDQS
Scored across 47 tools
Most tools target a distinct anchor or data source, and the search family is cleanly partitioned across source/docs, commits, tracker issues, rationale, and memories. A few near-overlaps exist—commit_search vs commits_touching_query and dream vs memory_doctor both touch stale-memory work—but explicit descriptions make misselection unlikely for most calls.
Names are uniformly snake_case and generally follow a readable pattern: verb_noun for operations like memory_create and find_callers, and domain_for_target for retrievals like papertrail_for_symbol and memory_for_path. Odd phrasings like commits_touching_query, compare_graph_to_text, and repo_clusters deviate from a strict verb_noun rhythm but remain predictable.
47 tools is a very large MCP surface, well beyond the 25-tool threshold the rubric flags as too many. The count is inflated by narrow query variants—papertrail_for_chunk/symbol/commit/path and memory_for_symbol/path/call_path could reasonably be parameterized anchors—so the set feels over-fragmented rather than tightly scoped.
The server covers the domain well: source/symbol/graph/history/tracker retrieval, a full memory lifecycle with edges, index maintenance, and a reviewable maintenance worklist. Minor gaps exist where required supporting actions are CLI-only, such as oracle run for SCIP comparisons and dream --verify/--compact, but core workflows have workarounds and do not dead-end.