hebros-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEBROS_ROOT | No | The root directory to index. If not set, Hebros indexes the folder it runs in. |
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 |
|---|---|
| get_mapA | Structure of a file or directory from the prebuilt index: every symbol with its line number and one-line signature, NO bodies. For a file, also shows what it imports (with each dependency's main exports) and who imports it. Cheaper than reading the whole file or globbing directories. Use BEFORE reading any file to decide which exact lines you need. |
| find_symbolA | Exact file:line where a function/class/interface/type/const is defined, from the symbol index. Use instead of grepping for definitions. Then read only that line range. |
| get_depsA | Import graph for one file OR a whole directory/package: what it imports and who imports it. Directory mode aggregates edges (N files -> target). Use for impact analysis before refactoring ("what breaks if I change this package?"). |
| get_referencesA | Where a symbol is used: JSX component usages, call sites (with line numbers), which files import it by name, and where the name is written without being called — string keys, object keys, property reads (how registries, event names and route tables wire things together). Use instead of grep-ing for usages. Heuristic — for a common name, narrow with file. |
| reindexA | Incremental git-based refresh (only changed files are re-parsed). Rarely needed — tools auto-refresh. |
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 primary intent, but get_map, get_references, and get_deps all overlap on reporting 'who imports it', and get_map and find_symbol both expose symbol locations. The descriptions mitigate the ambiguity, but an agent could still misselect for import/usage questions.
Most tools follow a verb_noun snake_case pattern (get_map, get_references, get_deps). find_symbol and reindex are minor deviations but still use the same action-first, lowercase-with-underscore style, so the naming remains predictable.
Five tools is a well-scoped count for a code-intelligence server. Each tool covers a distinct mode of interaction: refresh, definition lookup, structure overview, reference search, and dependency analysis.
The toolset covers the core workflow of navigating a codebase: locating definitions, browsing structure, finding usages, and analyzing dependency impact. The main gap is the lack of fuzzy or pattern-based symbol search, since find_symbol appears to require exact names.