mcp-code-context
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment, can be set to 'development' to enable debug logging. | development |
| LOG_LEVEL | No | Logging level: fatal, error, warn, info, debug, trace. | info |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_semantic_repo_mapB | Generate a compressed architectural overview of an entire repository |
| read_file_surgicalB | Read a file or extract a specific named symbol |
| analyze_impactC | Find all files that depend on a given file |
| read_file_linesC | Read specific line ranges from a file |
| search_code_patternC | Search for code patterns across multiple files |
| parse_fileC | Parse a file using Tree-sitter and extract symbols |
| write_file_surgicalA | Replace a symbol with new code. Phase 1 (dry-run): returns diff + token. Phase 2: confirm with token to apply. |
| insert_symbolA | Insert code at a specific location. Phase 1: returns diff + token. Phase 2: confirm with token to apply. |
| remove_symbolB | Remove a symbol from file. Phase 1: returns diff + token. Phase 2: confirm with token to apply. |
| rename_symbolA | Rename a symbol across the entire repository. Phase 1: returns diff + token. Phase 2: confirm with token to apply. |
| ast_transformA | Apply a declarative AST transformation to a symbol. Supports: add_parameter, wrap_with_try_catch, add_decorator, change_return_type, extract_variable. Uses two-phase write (Phase 1: preview diff, Phase 2: confirm with token). |
| search_symbolsA | Search symbols by name across the repo using AST (not text search). Finds classes, functions, methods by approximate name. |
| explain_symbolA | Get signature, location, and callers of a symbol in one call. More efficient than read_file_surgical + analyze_impact separately. |
| batch_readA | Read multiple symbols from multiple files in one call. Reduces N round-trips to 1. |
| get_rate_limit_statusA | Get current rate limiter token balance and operation costs. Use before expensive operations to check available budget. |
| rollback_fileC | Revert a file to its backup state |
| clean_backupsB | Remove all backup files for a project |
| get_server_statsA | Get server telemetry, audit statistics, and health metrics |
| get_cache_statsB | Get cache statistics (entries, size, hit rate) |
| clear_cacheB | Clear all cached parse results for a project |
| configure_file_watcherB | Start/stop file watcher for auto-cache invalidation |
| get_file_watcher_statusC | Get file watcher status for a project |
| get_session_statsB | Get statistics for the current MCP client session |
| clear_session_cacheA | Clear cache for current session only |
| list_pending_operationsB | List pending operations for crash recovery |
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 25 tools
Most tools have distinct purposes, but some overlap exists (e.g., read_file_surgical and explain_symbol both retrieve symbol information, though with different focuses). Descriptions generally clarify boundaries.
All tool names follow a consistent snake_case verb_noun pattern. Verbs like get_, read_, search_, and direct verbs (clean, clear, insert) are used uniformly per function.
With 25 tools, the server is at the high end of the 'heavy' range. While the number is justified by the breadth of features (reading, writing, analysis, state management), it feels slightly bloated for a typical code context server.
The tool surface covers core read, write, search, and analysis operations well. However, there is no explicit create/delete file tool, and file-level operations are limited, leaving minor gaps.