ue-codegraph-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_codebaseA | Register and index a UE source or project codebase. Scans C++ files, extracts symbols, UE macros, call graphs, and include dependencies. |
| get_index_statusB | Get the indexing status and statistics for registered codebases. |
| reindex_fileB | Re-index a single file (useful after file changes). |
| find_callersB | Find all functions that call a specific function. |
| find_calleesC | Find all functions called by a specific function. |
| find_call_chainB | Find the shortest call chain from one function to another using recursive CTE graph traversal. |
| get_file_dependenciesB | Get #include dependency graph for a file (what it includes and what includes it). |
| analyze_classA | Get detailed analysis of a C++ class including methods, properties, UE macros, inheritance, and Blueprint exposure. |
| get_class_hierarchyB | Get the inheritance hierarchy for a class (ancestors, descendants, or both). |
| find_ue_macrosA | Search for UE macros (UCLASS, UPROPERTY, UFUNCTION, etc.) with optional filtering by type and specifiers. |
| get_macro_specifiersC | Get all specifiers for a specific UE macro instance, including meta specifiers. |
| find_blueprint_exposedB | Find all Blueprint-exposed functions and properties across the codebase. |
| get_blueprint_interfaceA | Get the complete Blueprint interface for a class (all BP-exposed functions, properties, events, delegates). |
| find_referencesB | Find all references to a symbol (class, function, variable) across the codebase. |
| search_symbolsB | Search for symbols using full-text search (FTS5). Supports fuzzy matching. |
| search_codeC | Search through indexed code using text pattern matching. |
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 16 tools
Tools are mostly distinct with clear purposes, but find_callers, find_callees, and find_call_chain could be confused if not reading descriptions carefully. search_symbols and search_code have overlapping functionality but are differentiated by search type.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., init_codebase, find_callers, get_class_hierarchy). The verbs (init, get, find, analyze, search) are appropriate and predictable.
16 tools is well-scoped for a UE code analysis server, covering indexing, querying, and search without being overwhelming. Each tool serves a distinct purpose.
The tool set covers most aspects of codebase analysis: indexing, call graphs, class analysis, Blueprint exposure, macros, and search. Missing a tool to unregister/delete a codebase, but core workflows are complete.