A
licenseA
qualityA
maintenanceMCP server for semantic code search with AST-aware chunking, hybrid vectors, and query syntax.
12
1
Apache 2.0
github-code-rag-mcp
by suyu-creator
Related Servers
Alternatives to github-code-rag-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that helps coding agents research and prepare GitHub contributions by gathering repository guidance, related work, code context, and validation evidence into a local SQLite corpus, without ever writing to GitHub.2463MIT
- AlicenseNot gradedqualityFmaintenanceSelf-hosted MCP server for indexing and searching code repositories via hybrid search and deep code understanding.1018MIT
- AlicenseNot gradedqualityDmaintenanceIntelligent code search MCP server with AST analysis, call graphs, dependency tracking, and semantic embeddings for developers.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server for indexing source code from repositories into a Neo4j graph database and enabling Graph RAG-based search and traversal of functions via natural language queries.-
- AlicenseNot gradedqualityCmaintenanceMCP server for semantic code search and dependency graph analysis. Indexes codebases into a knowledge graph with vector embeddings for AI-powered code understanding.38MIT
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation3/5
Most tools have clear, distinct roles in the fetch-index-search workflow, but search_github and web_search_github both search for repositories and differ mainly in backend/fallback behavior, which can cause misselection. index_status and db_inspect also overlap as inspection tools, though descriptions clarify that db_inspect is more detailed.
Naming Consistency4/5
The majority of tools follow a clear verb_noun pattern: list_github_files, read_github_file, search_code, search_history, and search_github. A few outliers like db_inspect and db_cleanup put the object first, but the overall convention is still readable and predictable.
Tool Count5/5
Nine tools is well-scoped for a GitHub code retrieval and RAG workflow. Each tool covers a meaningful step in the pipeline—discovery, browsing, reading, indexing, searching, history lookup, and maintenance—without unnecessary bloat.
Completeness4/5
The tool surface covers the full workflow from GitHub repo discovery to file browsing, content reading, local indexing, code search, and database maintenance. Minor gaps exist, such as no direct GitHub-wide code search and some redundancy between search_github and web_search_github, but agents can complete the intended workflow without dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues