CodeGraph Multi-Repo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEGRAPH_MULTI_REPO_CONFIG | No | Path to the repos.yaml configuration file. Default is ~/.config/codegraph-multi-repo-mcp/repos.yaml |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reposA | List repositories configured for multi-repo CodeGraph exploration. |
| refresh_reposC | Refresh repository metadata and optionally include |
| explore_repoC | Explore one configured repository with |
| ask_multi_repoC | Route a question to multiple repositories and run CodeGraph exploration. |
| trace_across_reposC | Trace an identifier such as a symbol, API route, topic, DTO, or table across repositories. |
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 5 tools
Each tool has a clearly distinct purpose: listing repos, exploring one repo, refreshing metadata, asking questions across repos, and tracing identifiers across repos. No overlapping functionality.
All tool names follow the verb_noun pattern in snake_case (e.g., ask_multi_repo, explore_repo), maintaining perfect consistency across the set.
With 5 tools, the server is well-scoped for multi-repo CodeGraph exploration. Each tool serves a necessary function without redundancy or overload.
The tools cover core operations: listing, exploring, querying, tracing, and refreshing. Minor gaps exist, such as lacking a tool to add/remove repositories or search within a single repo without full exploration, but these are not critical.