omni-rag-mcp
Related Servers
Alternatives to omni-rag-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides LLM-optimized tools for advanced code analysis, repository complexity evaluation, and call graph generation. It enables users to visualize directory structures, detect code patterns, and build semantic context with significant token savings.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding assistants with deep, semantic understanding of local codebases via AST-aware chunking, cross-repo symbol graphs, and architectural memory, enabling context-aware code search and dependency tracing.10MIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic code search across multiple repositories using AST-aware chunking and relationship tracking. Supports local LLM embeddings, real-time indexing, and cross-codebase dependency analysis through vector and graph databases.3MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and IDEs to ingest and search code repositories using hybrid retrieval (dense + sparse) with exact line-level citations for precise code analysis.1-
- AlicenseNot gradedqualityCmaintenanceProvides Claude Code with local semantic search and indexing of your codebase using AST-aware chunking and hybrid search, enabling deep code understanding without sending data to the cloud.MIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic code search across multiple repositories using natural language queries. Provides intelligent code discovery, symbol lookups, and cross-repo dependency analysis for AI coding agents.MIT
TDQS
Scored across 14 tools
Several tools are exact duplicates of others, with one marked deprecated and one current (e.g., check_index_status vs check_status). This creates ambiguity as an agent cannot easily distinguish which to use, leading to potential misselection.
Naming is somewhat consistent with a verb_noun pattern (e.g., search, search_by_file, ingest, stats), but deprecated tools use inconsistent forms like check_index_status and get_codebase_context, breaking the pattern.
With 14 tools, the count is reasonable for a RAG server. However, 6 of them are deprecated, reducing the effective set to 8 well-scoped tools, which is appropriate for the domain.
The toolset covers key operations: index status, context overview, search (including file-filtered), statistics, ingestion, dependency graph, and file signatures. Missing explicit index deletion or update, but core workflows are covered.