Code Reference Optimizer MCP Server

An advanced MCP (Model Context Protocol) server that intelligently extracts minimal, relevant code context using AST parsing, analyzes code differences, and optimizes imports to dramatically reduce token usage for AI assistants.

Key Features

• Smart Context Extraction: Uses AST parsing to identify and extract only relevant code sections
• Multi-language Support: TypeScript/JavaScript, Python, Go, Rust, Java, C++, and more
• Intelligent Caching: LRU cache with configurable persistence and customizable storage paths
• Token Optimization: Filters unnecessary code while maintaining semantic completeness
• Diff Analysis: Provides minimal, focused code differences with semantic understanding
• Import Optimization: Eliminates unused imports and suggests consolidation opportunities
• Configurable: Runtime configuration via tools with persistent settings
• Simple Integration: stdio-based server and optional HTTP server, easy to integrate with any MCP client

Quick Start (STDIO)

• One-off (recommended):

npx -y @fosterg4/mcpsaver

You should see: Code Reference Optimizer MCP server running on stdio.

• Global (optional):

npm i -g @fosterg4/mcpsaver
mcpsaver

HTTP Mode

Start the HTTP server on port 8081 (default):

npx -y @fosterg4/mcpsaver mcpsaver-http
# or after build
npm run start:http

Configure your MCP client to use the HTTP binary if supported, e.g.:

{
  "mcpServers": {
    "mcpsaver": { "command": "mcpsaver-http", "env": { "PORT": "8081", "LOG_LEVEL": "info" } }
  }
}

Use with an MCP client

Add to your MCP client config (example mcpServers.json):

{
  "mcpServers": {
    "mcpsaver": {
      "command": "npx",
      "args": ["-y", "@fosterg4/mcpsaver"],
      "env": {}
    }
  }
}

Available Tools

The server provides 7 powerful tools for code analysis and optimization:

🔍 extract_code_context

Extracts minimal, focused code context using AST parsing. Intelligently identifies relevant code sections, imports, and dependencies for specific symbols.

{
  "filePath": "path/to/file.ts",
  "targetSymbols": ["myFunc", "MyClass"],
  "includeImports": true,
  "maxTokens": 1000
}

Required: filePath | Optional: targetSymbols, includeImports, maxTokens

💾 get_cached_context

Retrieves previously extracted and cached code context for fast access without re-parsing.

{ "filePath": "path/to/file.ts", "cacheKey": "optional-key" }

Required: filePath | Optional: cacheKey

📊 analyze_code_diff

Performs intelligent analysis of code differences with semantic understanding and minimal update suggestions.

{
  "filePath": "path/to/file.ts",
  "oldContent": "export function a() { return 1 }",
  "newContent": "export function a() { return 2 }"
}

Required: filePath, oldContent, newContent

🧹 optimize_imports

Analyzes and optimizes import statements to eliminate redundancy and improve code efficiency.

{ "filePath": "path/to/file.ts", "usedSymbols": ["useEffect", "useMemo"] }

Required: filePath | Optional: usedSymbols

⚙️ get_config

Retrieves current configuration settings for cache behavior, extraction parameters, and more.

{ "section": "cache" }

Optional: section (cache, extraction, imports, diff, performance, languages, logging, security)

🔧 update_config

Updates configuration settings including cache policies, token limits, and performance thresholds.

{
  "config": {
    "cache": { "enablePersistence": true, "persistencePath": "/custom/cache/path" },
    "extraction": { "maxTokens": 2000 }
  }
}

Required: config

🔄 reset_config

Resets all configuration settings to default values.

{}

No parameters required

Note: Tool results are returned as MCP content with a single text item containing JSON of the result, e.g.

{
  "content": [{ "type": "text", "text": "{\n  \"...\": true\n}" }]
}

Additional MCP Capabilities

• Prompts: listed but empty; get_prompt returns MethodNotFound.
• Resources: listed but empty; reading a resource returns MethodNotFound.
• Roots: exposes the current working directory as a single root workspace.
• Sampling: stubbed; sampling/createMessage returns MethodNotFound.

Examples

See docs/EXAMPLES.md for end‑to‑end request examples of each tool.

Configuration

• Call get_config, update_config, reset_config to manage runtime settings.
• You may also set environment variables via your MCP client if supported (e.g., LOG_LEVEL).

Structured Logging

The server uses a lightweight structured logger. Configure via get_config/update_config or env:

• Level: config.logging.level (trace|debug|info|warn|error)
• File logging: config.logging.enableFileLogging and config.logging.logPath

Development

npm ci
npm run build
npm start     # run built server (stdio)
npm run start:http # run built server (http)
npm run dev   # tsc --watch
npm test
npm run lint
npm run type-check

Publishing (maintainers)

npm login
npm run clean && npm run build
npm version patch
npm publish --access public

License

MIT — see LICENSE.