intelligraph-mini
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| repo-dir | Yes | The directory of the repository to analyze (e.g., '.' for current directory) |
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 |
|---|---|
| searchA | Search the codebase for symbols, files, or concepts. Works equally well for exact names ('UserStatus'), file paths ('types/enums'), or natural language ('how authentication works'). Returns name, kind, file path with line ranges (file:start-end), and confidence [H/M/L]. Use built-in Read with offset=line_start, limit=line_end-line_start to get source. Use this FIRST — replaces grep and glob. |
| nodeA | Get a symbol's connections (callers, callees, imports) with file:line ranges. Use AFTER search. Then use built-in Read with those line ranges to get implementation details. Replaces reading whole files — read only the specific line ranges shown. |
| pathC | Trace the shortest path between two symbols in the codebase graph. |
| impactA | Complete blast radius of changing a symbol. Exhaustive traversal of ALL edge types. Returns every affected file with symbols to check. Use before refactoring. Files not listed do not depend on the target. |
| local_filesA | Read full source files from disk. EXPENSIVE. Prefer built-in Read with line ranges from search/node results instead. Use this only when you need a whole file that search/node didn't cover. |
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 distinct role: search locates symbols, node shows connections, path finds shortest routes, impact assesses blast radius, and local_files reads source. No two tools overlap in purpose.
Names are mostly single-word and lowercase, but mix verbs (search) and nouns (node, path, impact, local_files). The underscore in local_files is inconsistent with the other names, though still readable.
Five tools is well-scoped for a mini code-graph intelligence server, covering search, exploration, pathfinding, impact analysis, and file reading without redundancy.
The set covers the full analysis workflow: locate, explore, trace, assess, and read. Instructions to use built-in Read with line ranges fill any need for source access, leaving no obvious gaps.