code-context
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CC_WATCH | No | Enable file watching: 'on' or 'off' (default: 'off') | off |
| CC_CHUNKER | No | Chunking strategy: 'treesitter' (default) or 'line' | treesitter |
| CC_CACHE_DIR | No | Path to cache directory (default: platformdirs user cache) | |
| CC_TELEMETRY | No | Opt-in telemetry: 'on' or 'off' (default: 'off') | off |
| CC_EMBEDDINGS | No | Embeddings backend: 'local' (default) or 'openai' | local |
| OPENAI_API_KEY | No | OpenAI API key (required if CC_EMBEDDINGS=openai) | |
| CC_EMBEDDINGS_MODEL | No | Model for embeddings (e.g., 'all-MiniLM-L6-v2') | all-MiniLM-L6-v2 |
| CC_WATCH_DEBOUNCE_MS | No | Debounce interval for file watching in milliseconds (default: '1000') | 1000 |
| CC_EMBEDDINGS_BACKEND | No | Embeddings runtime: 'onnx' (default) or 'torch' | onnx |
| CC_INCLUDE_EXTENSIONS | No | Comma-separated list of file extensions to index | .py,.js,.ts,.jsx,.tsx,.go,.rs,.java,.c,.cpp,.h,.hpp,.md,.yaml,.yml,.json |
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 |
|---|---|
| search_repoA | Semantic search over the indexed codebase. Use this INSTEAD of Grep when the query is conceptual (e.g. 'where do we validate input', 'how is caching implemented', 'authentication flow'). Returns ranked code fragments with file path, line range, snippet, score and a one-line |
| recent_changesA | Recent git commits with structured fields (sha, ISO date, author, paths, summary). Use INSTEAD of |
| get_summaryA | Structured snapshot of the project or a module: name, purpose (README first paragraph), stack (Python/Node/Rust/Go/Java), entry_points, key_modules, stats (files, loc, languages). Useful at session start for orientation; prefer it over reading README/CLAUDE.md when you need machine-readable fields. |
| find_definitionA | Locate the definition site of a named symbol (function, class, method, type, struct, enum, interface, record). Use this INSTEAD of shelling out to grep when the user asks "where is X defined?" — returns SymbolDef[] with path, line range, kind, and language. Faster and more accurate than grepping for |
| find_referencesA | List every textual occurrence of a named symbol in the indexed corpus. Use INSTEAD of |
| get_file_treeA | Repo-relative directory tree, gitignore-aware. Use INSTEAD of shelling out to |
| explain_diffA | AST-aligned chunks affected by the diff at |
| refreshA | Trigger a background reindex without restarting the server. Use after large external changes (git checkout, cache import, file restore). By default blocks until the new index is active (60s timeout). Pass |
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
All 8 tools have clearly distinct purposes, with no overlap. Each tool's description explicitly states when to use it instead of alternatives, making it easy for an agent to select the correct tool.
Tool names consistently use lowercase with underscores, following a verb_noun pattern (e.g., find_definition, get_file_tree, search_repo). The only exception is 'refresh', which is a verb alone but still fits the action-oriented style.
With 8 tools, the server is well-scoped for a code context assistant. Each tool provides essential functionality without redundancy, covering diff analysis, symbol navigation, project structure, git history, and reindexing.
The tool surface comprehensively covers the code context domain: diff explanation, symbol definition/references, file tree, project summary, recent changes, reindexing, and semantic search. No obvious gaps exist for typical code understanding tasks.