Code Reference Optimizer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | The logging level for the server |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_code_contextC | Extract minimal code context from files using AST parsing |
| get_cached_contextB | Retrieve cached code context for a file |
| analyze_code_diffC | Analyze differences between code versions and provide minimal updates |
| optimize_importsC | Analyze and optimize import statements to reduce redundancy |
| get_configC | Get current configuration settings |
| update_configC | Update configuration settings |
| reset_configB | Reset configuration to default values |
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 7 tools
Each tool has a clearly distinct purpose with no ambiguity: analyze_code_diff handles code version comparisons, extract_code_context and get_cached_context manage code context retrieval (one for extraction, one for caching), get_config, update_config, and reset_config handle configuration operations, and optimize_imports focuses on import optimization. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent verb_noun pattern using snake_case, such as analyze_code_diff, extract_code_context, and optimize_imports. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With 7 tools, the count is well-scoped for a code reference optimizer server. Each tool serves a specific role in code analysis, context management, and configuration, with no apparent bloat or missing essential functions, fitting the server's purpose appropriately.
The tool set covers core areas like code analysis, context extraction/caching, and configuration management, providing good lifecycle coverage. A minor gap exists in direct code editing or refactoring tools beyond imports, but agents can work around this using the provided tools for most optimization tasks.