github-codemunch-mcp
Related Servers
Alternatives to github-codemunch-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server for efficient code indexing and symbol retrieval using tree-sitter AST parsing to fetch specific functions or classes without loading entire files. It significantly reduces AI token costs by providing O(1) byte-offset access to code components across multiple programming languages.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides ultra-efficient code exploration through AST analysis, reducing LLM token usage by up to 95% while enabling instant call graph generation and dependency analysis for massive codebases.MIT
- AlicenseNot gradedqualityCmaintenanceA persistent, tree-sitter-backed code knowledge cache MCP server that reduces token usage by storing parsed structure and enabling fast symbol lookup, inheritance graph, call graph, and semantic search.1MIT
- AlicenseNot gradedqualityCmaintenanceToken-efficient code intelligence MCP server that indexes codebases with tree-sitter AST parsing and provides 150 tools for AI agents, using 61-95% fewer tokens than traditional grep/Read workflows.91 npm4Business Source 1.1
- AlicenseNot gradedqualityCmaintenanceToken-efficient MCP server for multi-language project analysis (Java, TypeScript, JavaScript, Markdown, Python) with plugins, semantic search, and static analysis.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides structure-aware code analysis (symbol trees, dependencies, docs) to reduce AI agent token consumption by up to 99%, along with Git commit intelligence.MIT
TDQS
Scored across 7 tools
Most tools have distinct purposes, but get_symbol and get_symbols could be confused as they both retrieve symbol source code, differing only in single vs. multiple symbols. The descriptions clarify this, but the naming similarity creates minor ambiguity. Other tools like get_file_outline, get_file_tree, and search_symbols are clearly differentiated.
All tool names follow a consistent verb_noun pattern with snake_case, such as get_file_outline, index_repo, and search_symbols. There are no deviations in naming conventions, making the set predictable and easy to parse for agents.
With 7 tools, the count is well-scoped for the server's purpose of indexing and querying GitHub repository code. Each tool serves a specific function in the workflow, from indexing and listing repos to retrieving file structures and symbols, without unnecessary redundancy.
The toolset covers core workflows for code indexing and symbol retrieval, including repository management, file exploration, and symbol search. A minor gap exists in update or delete operations for indexed repos, but agents can work around this, and the surface is largely complete for the stated domain.