MCP Codebase RAG Server
Related Servers
Alternatives to MCP Codebase RAG Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that provides semantic search (RAG) over code repositories, enabling AI clients like Claude and Gemini to access project context without manual re-upload.-
- AlicenseNot gradedqualityAmaintenanceLocal MCP server to index your codebase once and search it across AI sessions with keyword, semantic, or hybrid search, keeping all data on disk.52 npm3MIT
- AlicenseNot gradedqualityBmaintenanceA local hybrid-search MCP server that enables coding agents to query files and folders using natural language, returning relevant code chunks with exact source paths. Everything runs on-device with no API keys or network calls.9MIT
- AlicenseAqualityCmaintenanceA fully local RAG MCP server for semantic code search and code intelligence, using AST-level chunking and hybrid search to pinpoint functions, classes, and APIs. No cloud, no API keys, zero setup.1647 npm13MIT
- AlicenseAqualityDmaintenanceLocal-first MCP server for semantic + keyword hybrid code search. Zero external services, no API keys required.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to index code repositories and run AST-aware semantic and hybrid keyword search across files, commits and branches, returning relevant code snippets with expanded file context. It handles incremental re-indexing with local embeddings and Qdrant storage, and can serve either over stdio or as a bearer-token-protected HTTP endpoint for remote or containerized use.7 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: search, reindex, list projects, list files, and get file content. There is no meaningful overlap; even the two 'get' tools are unambiguous because one returns metadata for files and the other returns the actual content.
All tool names follow a consistent verb_noun pattern: search_codebase, reindex_project, list_indexed_projects, get_files, get_file_content. The verbs are distinct and descriptive, and the pattern is uniformly applied without mixing styles.
With 5 tools, the server is well-scoped for a codebase RAG system. Each tool addresses a core need (indexing, search, and file retrieval) without unnecessary bloat, fitting comfortably in the ideal range and making the surface easy to navigate.
The tool set covers the primary lifecycle: index (reindex), list indexed projects, search, list files, and fetch file content. Minor gaps exist, such as no explicit delete project or incremental update mechanism, but these are not critical for core RAG workflows and can be worked around.