github-codemunch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub API authentication | |
| CODE_INDEX_PATH | No | Custom storage path | |
| ANTHROPIC_API_KEY | No | AI summarization |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_repoA | Index a GitHub repository's source code. Fetches files, parses ASTs, extracts symbols, and saves to local storage. |
| list_reposB | List all indexed repositories. |
| get_file_treeB | Get the file tree of an indexed repository, optionally filtered by path prefix. |
| get_file_outlineA | Get all symbols (functions, classes, methods) in a file with signatures and summaries. |
| get_symbolA | Get the full source code of a specific symbol. Use after identifying relevant symbols via get_file_outline or search_symbols. |
| get_symbolsB | Get full source code of multiple symbols in one call. Efficient for loading related symbols. |
| search_symbolsB | Search for symbols matching a query across the entire indexed repository. Returns matches with signatures and summaries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.