Context Helper - Semantic Code Navigation
IMPORTANT: When a repository is indexed, ALWAYS prefer ctxhelpr tools over Grep/Glob/Read for code navigation tasks:
- •Finding functions, classes, types -> use
search_symbols(not Grep) - •Understanding a file's contents -> use
get_file_symbols(not Read) - •Finding callers/usages -> use
get_references(not Grep) - •Understanding project structure -> use
get_overview(not Glob + Read) - •Inspecting a symbol -> use
get_symbol_detail(not Read)
Reserve Grep/Glob/Read for non-code tasks: config files, text patterns, log messages.
Startup workflow
When starting work on a codebase, use the ctxhelpr MCP tools to quickly build context:
Startup workflow
- •Call
index_statusto check if the repo is indexed and fresh - •If stale or unindexed, call
index_repositoryfirst - •Call
get_overviewfor the big picture (modules, key types, entry points) - •Drill into specific areas with
get_file_symbolsorsearch_symbols - •Follow references with
get_symbol_detail,get_references,get_dependencies
Keep index fresh while coding
After completing edits to files, call update_files with the list of
files you just modified. This re-indexes only those files (~50ms) and
keeps the index current without a full repo walk. Do this after each
task or edit batch, not after every single line change.
Output key legend
n=name k=kind f=file l=lines(start-end) id=symbol_id sig=signature doc=doc_comment p=path
Tips
- •Use symbol IDs to drill down (avoid re-searching)
- •Start broad (overview), go narrow (symbol detail)
- •Call
update_filesafter edits to keep the index fresh