code_nav 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 |
|---|---|
| code_nav.healthA | Check repo detection and code_nav dependency health. |
| code_nav.find_fileA | Find repo-relative files with fff or git-visible fallback. |
| code_nav.exact_searchC | Ranked candidate exact text search; not exhaustive proof. |
| code_nav.exact_auditC | Exhaustive exact audit using raw rg or git grep. |
| code_nav.extract_contextC | Extract compact code context with Probe or fallback ranges. |
| code_nav.structural_searchC | AST/code-shape search using ast-grep or sg. |
| code_nav.coverageA | Show git-visible file coverage; no semantic index exists. |
| code_nav.searchD | Main deterministic code navigation workflow. |
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 8 tools
Each tool has a distinct purpose: coverage, exact audit, exact search, context extraction, file finding, health check, main search workflow, and structural search. No significant overlap; an agent can easily differentiate them.
All tools follow a consistent prefix 'code_nav.' and use lowercase with underscores. However, the action part varies between nouns (e.g., 'coverage', 'health') and verb_noun patterns (e.g., 'find_file', 'extract_context'), showing minor inconsistency.
With 8 tools, the set is well-scoped for code navigation. Each tool serves a clear function, and the count feels appropriate without being excessive or too sparse.
The tools cover a broad range of code navigation tasks: text search, structural search, file finding, coverage, and context extraction. Minor gaps exist like symbol search or definition lookup, but core workflows are well-supported.