mcp-code-context 2.5.1 → 3.0.4

package/llms.txt

@@ -1,234 +1,246 @@
-# mcp-code-context v2.5.0
-
-> A Model Context Protocol (MCP) server that compresses any code repository into LLM-ready semantic context and provides surgical code editing tools.
-
-## What's New in v2.4.1
-
-🐛 **Bug Fix**: analyze_impact now works correctly
-- ✅ Fixed TypeScript ESM import resolution
-- ✅ Correctly detects dependencies in TypeScript projects
-
-## What's New in v2.4.0
-
-🚀 **Performance Revolution**: Fully async I/O architecture
-- ✅ All blocking file operations eliminated
-- ✅ 3x faster on repositories with 1000+ files
-- ✅ Non-blocking event loop (was blocking in v2.3.x)
-- ✅ +300% throughput on large codebases
-- ✅ Scalability score: 4.0 → 9.0
-
-## What This Tool Does
-
-This MCP server solves two problems:
-1. **Token bloat on reads**: When an LLM needs to understand a large codebase, sending raw source files wastes most of the context window. This server extracts only structural signatures.
-2. **Imprecise writes**: When an LLM needs to edit code, rewriting entire files is error-prone and expensive. This server enables symbol-level surgical edits.
-
-## Available Tools
-
-### Read Tools
-
-#### 1. `get_semantic_repo_map`
-**Purpose:** Generate a compressed architectural map of an entire repository.
-
-**Input:**
-- `directoryPath` (required): Absolute path to the repository root.
-- `format` (optional): `"xml"` (default) or `"markdown"`.
-
-**What it does:**
-- Walks the directory tree respecting `.gitignore` and `.repomixignore` rules.
-- Always excludes `node_modules`, `dist`, `build`, `vendor`, `.git`.
-- For TypeScript/JavaScript: Uses AST parsing (ts-morph) to extract only function signatures, class structures, interfaces, types, and enums.
-- For PHP: Uses AST parsing (php-parser) to extract namespaces, classes, interfaces, traits, enums, methods, properties, and docblocks.
-- For Dart: Uses brace-counting + regex engine to extract classes, mixins, extensions, enums, methods, and fields.
-- For Python: Uses regex-based extraction to capture class/function signatures and docstrings.
-- For other files: Returns content as-is if small, or a truncated preview if large.
-
-**Best used when:** You need to understand the architecture of a project before diving into specific files.
-
-#### 2. `read_file_surgical`
-**Purpose:** Read a full file or extract only a specific named symbol.
-
-**Input:**
-- `filePath` (required): Absolute path to the source file.
-- `symbolName` (optional): Name of a function, class, interface, method, or type to extract.
-
-**What it does:**
-- With `symbolName`: Parses the AST and returns only the full source code block for that symbol. Saves tokens when you only need one function from a large file.
-- If missing: Returns structured JSON with `available_symbols` and `suggestions` (e.g., suggesting a `className` scope).
-
-**Best used when:** You identified a symbol from the repo map and need to see its full implementation.
-
-#### 3. `analyze_impact`
-**Purpose:** Find all files that depend on a given file.
-
-**Input:**
-- `filePath` (required): Absolute path to the file being modified.
-- `rootDir` (optional): Repository root. Auto-detected if omitted.
-
-**What it does:**
-- Scans all source files for `import`, `require()`, Python `from/import`, PHP `use`/`require_once`/`include`, and Dart `import` statements.
-- Resolves relative paths to determine if they point to the target file.
-- Returns a structured report listing every dependent file and the specific import statement.
-
-**Best used when:** You're about to modify a file and need to understand the blast radius.
-
-#### 4. `read_file_lines`
-**Purpose:** Read specific line ranges from a file without loading the entire content.
-
-**Input:**
-- `filePath` (required): Absolute path to the source file.
-- `startLine` (optional): Starting line number (1-indexed).
-- `endLine` (optional): Ending line number (1-indexed).
-- `aroundPattern` (optional): Search pattern to find and return surrounding lines.
-- `contextLines` (optional): Number of lines before/after pattern (default: 5).
-
-**What it does:**
-- **Mode 1 (Exact Range)**: When `startLine` and `endLine` are provided, returns only those lines.
-- **Mode 2 (Pattern Search)**: When `aroundPattern` is provided, finds the first occurrence and returns surrounding lines with context.
-- Validates line ranges and provides clear error messages.
-- 90% token savings compared to reading full files for small fragments.
-
-**Best used when:** 
-- Debugging specific code blocks when you know the line numbers
-- Viewing context around error messages or logs
-- Extracting small fragments without AST parsing overhead
-
-**Example use cases:**
-- "Show me lines 120-135 of coordinator.dart"
-- "Show me the code around 'HeroBannerWidget' in hero_banner_widget.dart"
-
-#### 5. `search_code_pattern`
-**Purpose:** Search for code patterns across multiple files in a repository.
-
-**Input:**
-- `rootDir` (required): Absolute path to the repository root.
-- `pattern` (required): Regular expression pattern to search for.
-- `fileExtensions` (optional): Array of extensions to search (e.g., `[".ts", ".dart"]`). Defaults to common code extensions.
-- `excludeDirs` (optional): Directories to exclude (default: `["node_modules", "dist", "build"]`).
-- `showContext` (optional): Include surrounding lines (default: true).
-- `contextLines` (optional): Number of context lines before/after (default: 3).
-- `maxResults` (optional): Maximum matches to return (default: 50).
-
-**What it does:**
-- Walks the repository respecting `.gitignore` rules.
-- Searches for regex patterns across all matching files.
-- Returns structured results with file paths, line numbers, and optional context.
-- Highlights the matching line with a `>` marker in context output.
-- 85% more efficient than manual grep + analysis workflows.
-
-**Best used when:**
-- Finding all usages of a function or variable
-- Locating specific log statements or debug markers
-- Discovering patterns across the codebase
-- Understanding how a feature is implemented across files
-
-**Example use cases:**
-- "Find all occurrences of 'widget.height' in the Flutter project"
-- "Search for '🎯 \[BUILDER\]' logs in .dart files"
-- "Find all files that call 'HeroBannerWidget'"
-
-#### 6. `rollback_file`
-**Purpose:** Restores a file to a previous state from the automated backup system.
-**Input:**
-- `filePath` (required): Absolute path.
-- `steps` (optional): Number of versions to go back (1-5, default: 1).
-**What it does:** Reverts the file to the state it was in before the last 1-5 modifications.
-
-### Write Tools (v2.2.0 Mandatory Workflow)
-
-All write tools follow a **Two-Phase Workflow**:
-1. **Phase 1 (Preview)**: Call without a token to get a unified `diff` and a `confirmationToken`.
-2. **Phase 2 (Apply)**: Call with `confirmationToken` and `confirm: true` to apply the changes.
-
-**Important Notes (v2.2.0):**
-- ✅ **Windows CRLF Support**: Fully resolved. All operations work correctly on Windows files with CRLF line endings.
-- ✅ **Parameter Brace Handling**: Methods with braces in parameters (e.g., `{int? cart}`) are now handled correctly.
-
-#### 7. `write_file_surgical`
-**Purpose:** Replace the full source code of a named symbol in a file.
-
-**Input:**
-- `filePath` (required): Absolute path to the file to modify.
-- `symbolName` (required): Name of the symbol to replace.
-- `newContent` (required): Complete replacement code (signature + body).
-- `confirmationToken` (optional): Token from Phase 1.
-- `confirm` (optional): Set to `true` to apply.
-- `className` (optional): Scope the symbol to a specific class.
-
-**What it does:**
-- Locates the symbol via AST parsing (ts-morph, php-parser, brace-counting, or indentation detection).
-- Replaces only that symbol's code, preserving all other file contents.
-- Returns a unified diff showing exactly what changed.
-- Validates the result is syntactically valid before writing.
-
-**Best used when:** You need to modify a specific function or method without touching the rest of the file.
-
-#### 8. `insert_symbol`
-**Purpose:** Insert new code at a precise location relative to an existing symbol.
-
-**Input:**
-- `filePath` (required): Absolute path to the file.
-- `code` (required): The new code to insert.
-- `anchorSymbol` (optional): Symbol name to position relative to. If omitted, inserts at end of file.
-- `position` (optional): `"before"`, `"after"`, `"inside_start"`, `"inside_end"`. Defaults to `"after"`.
-- `confirmationToken`, `confirm` (optional): Standard Phase 2 parameters.
-
-**What it does:**
-- Finds the anchor symbol and inserts new code at the specified position.
-- Automatically matches the surrounding indentation style.
-- `inside_start` and `inside_end` insert as members inside a class or interface.
-
-**Best used when:** Adding new methods to a class or new functions to a module.
-
-#### 9. `rename_symbol`
-**Purpose:** Rename a symbol across an entire repository.
-
-**Input:**
-- `filePath` (required): File where the symbol is defined.
-- `oldName` (required): Current name.
-- `newName` (required): New name.
-- `rootDir` (optional): Repository root. Auto-detected if omitted.
-- `confirmationToken`, `confirm` (optional): Standard Phase 2 parameters.
-
-**What it does:**
-- Renames the symbol definition in the source file.
-- Finds all dependent files using import analysis.
-- Renames all references in dependent files using whole-word replacement.
-- Returns a multi-file diff showing all changes.
-- Rolls back all changes if any file write fails.
-
-**Best used when:** Refactoring a class, function, or method name that is used across multiple files.
-
-#### 10. `remove_symbol`
-**Purpose:** Safely remove a symbol from a file.
-
-**Input:**
-- `filePath` (required): Absolute path.
-- `symbolName` (required): Symbol to remove.
-- `force` (optional): If true, skip dependency check. Defaults to false.
-- `confirmationToken`, `confirm` (optional): Standard Phase 2 parameters.
-
-**What it does:**
-- Checks if other files reference the symbol (unless `force: true`).
-- If dependents exist, refuses to remove and reports which files use it.
-- If safe, removes the symbol's code and cleans up whitespace.
-
-**Best used when:** Cleaning up deprecated functions or unused code.
-
-## Recommended Workflow
-
-1. **Start with `get_semantic_repo_map`** to understand the project structure.
-2. **Use `read_file_surgical`** with a symbol name. Use suggestions if the symbol is missing.
-3. **Before modifying, run `analyze_impact`** to know the blast radius.
-4. **Phase 1: Preview Edit** → Call write tools to get a `diff` and `confirmationToken`.
-5. **Phase 2: Apply Edit** → Verify the diff, then call with the token and `confirm: true`.
-6. **Recovery** → Use `rollback_file` if needed.
-
-## Technical Details
-
-- **Transport:** stdio (JSON-RPC over stdin/stdout)
-- **Runtime:** Node.js >= 18
-- **AST Engines:** ts-morph (TypeScript/JS), php-parser (PHP), brace-counting/regex (Dart, Python)
-- **Ignore Engine:** `ignore` npm package (full .gitignore spec support)
-- **Supported languages:** TypeScript, JavaScript (all variants), PHP, Dart, Python
-- **Safety features:** Mandatory two-phase confirmation, rolling 5-version backups (`.mcp-backups/`), fuzzy symbol suggestions, dependency tracking, surgical restoration.
+# mcp-code-context v3.0.4
+
+> A Model Context Protocol (MCP) server with **Tree-sitter WASM parsers** for 100% AST accuracy. Zero native dependencies.
+
+## What's New in v3.0.4
+
+🔧 **npx Compatibility Fix**:
+- ✅ Fixed npx execution on Windows
+- ✅ Reverted to v2 build structure (dist/src/index.js)
+- ✅ Works with Claude Desktop using npx -y
+
+## What's New in v3.0.4
+
+🔧 **NPM Package Optimization**:
+- ✅ Package size reduced: 658.6 kB → 105.5 kB (-84%)
+- ✅ File count reduced: 131 files → 36 files (-73%)
+- ✅ Clean dist/ structure (no nested dist/src/)
+- ✅ Excluded legacy v2 code from npm distribution
+
+## What's New in v3.0.4
+
+🚀 **Complete WASM Migration**: 100% portable architecture
+- ✅ Migrated to web-tree-sitter@0.25.1 (WASM)
+- ✅ Zero native dependencies (no Visual Studio, node-gyp, Python)
+- ✅ Works on Windows/Mac/Linux without compilation
+- ✅ Dart with full Tree-sitter AST (no regex fallback)
+- ✅ TypeScript/JavaScript/Python/PHP all use WASM parsers
+- ✅ ABI v15 support (latest language grammars)
+
+## What This Tool Does
+
+This MCP server solves two problems:
+1. **Token bloat on reads**: When an LLM needs to understand a large codebase, sending raw source files wastes most of the context window. This server extracts only structural signatures.
+2. **Imprecise writes**: When an LLM needs to edit code, rewriting entire files is error-prone and expensive. This server enables symbol-level surgical edits.
+
+## Available Tools
+
+### Read Tools
+
+#### 1. `get_semantic_repo_map`
+**Purpose:** Generate a compressed architectural map of an entire repository.
+
+**Input:**
+- `directoryPath` (required): Absolute path to the repository root.
+- `format` (optional): `"xml"` (default) or `"markdown"`.
+
+**What it does:**
+- Walks the directory tree respecting `.gitignore` and `.repomixignore` rules.
+- Always excludes `node_modules`, `dist`, `build`, `vendor`, `.git`.
+- For TypeScript/JavaScript: Uses Tree-sitter WASM to extract function signatures, class structures, interfaces, types, and enums.
+- For PHP: Uses Tree-sitter WASM to extract namespaces, classes, interfaces, traits, enums, methods, properties.
+- For Dart: Uses Tree-sitter WASM to extract classes, mixins, extensions, enums, methods, and fields.
+- For Python: Uses Tree-sitter WASM to capture class/function signatures and docstrings.
+- For other files: Returns content as-is if small, or a truncated preview if large.
+
+**Best used when:** You need to understand the architecture of a project before diving into specific files.
+
+#### 2. `read_file_surgical`
+**Purpose:** Read a full file or extract only a specific named symbol.
+
+**Input:**
+- `filePath` (required): Absolute path to the source file.
+- `symbolName` (optional): Name of a function, class, interface, method, or type to extract.
+
+**What it does:**
+- With `symbolName`: Parses the AST and returns only the full source code block for that symbol. Saves tokens when you only need one function from a large file.
+- If missing: Returns structured JSON with `available_symbols` and `suggestions` (e.g., suggesting a `className` scope).
+
+**Best used when:** You identified a symbol from the repo map and need to see its full implementation.
+
+#### 3. `analyze_impact`
+**Purpose:** Find all files that depend on a given file.
+
+**Input:**
+- `filePath` (required): Absolute path to the file being modified.
+- `rootDir` (optional): Repository root. Auto-detected if omitted.
+
+**What it does:**
+- Scans all source files for `import`, `require()`, Python `from/import`, PHP `use`/`require_once`/`include`, and Dart `import` statements.
+- Resolves relative paths to determine if they point to the target file.
+- Returns a structured report listing every dependent file and the specific import statement.
+
+**Best used when:** You're about to modify a file and need to understand the blast radius.
+
+#### 4. `read_file_lines`
+**Purpose:** Read specific line ranges from a file without loading the entire content.
+
+**Input:**
+- `filePath` (required): Absolute path to the source file.
+- `startLine` (optional): Starting line number (1-indexed).
+- `endLine` (optional): Ending line number (1-indexed).
+- `aroundPattern` (optional): Search pattern to find and return surrounding lines.
+- `contextLines` (optional): Number of lines before/after pattern (default: 5).
+
+**What it does:**
+- **Mode 1 (Exact Range)**: When `startLine` and `endLine` are provided, returns only those lines.
+- **Mode 2 (Pattern Search)**: When `aroundPattern` is provided, finds the first occurrence and returns surrounding lines with context.
+- Validates line ranges and provides clear error messages.
+- 90% token savings compared to reading full files for small fragments.
+
+**Best used when:** 
+- Debugging specific code blocks when you know the line numbers
+- Viewing context around error messages or logs
+- Extracting small fragments without AST parsing overhead
+
+**Example use cases:**
+- "Show me lines 120-135 of coordinator.dart"
+- "Show me the code around 'HeroBannerWidget' in hero_banner_widget.dart"
+
+#### 5. `search_code_pattern`
+**Purpose:** Search for code patterns across multiple files in a repository.
+
+**Input:**
+- `rootDir` (required): Absolute path to the repository root.
+- `pattern` (required): Regular expression pattern to search for.
+- `fileExtensions` (optional): Array of extensions to search (e.g., `[".ts", ".dart"]`). Defaults to common code extensions.
+- `excludeDirs` (optional): Directories to exclude (default: `["node_modules", "dist", "build"]`).
+- `showContext` (optional): Include surrounding lines (default: true).
+- `contextLines` (optional): Number of context lines before/after (default: 3).
+- `maxResults` (optional): Maximum matches to return (default: 50).
+
+**What it does:**
+- Walks the repository respecting `.gitignore` rules.
+- Searches for regex patterns across all matching files.
+- Returns structured results with file paths, line numbers, and optional context.
+- Highlights the matching line with a `>` marker in context output.
+- 85% more efficient than manual grep + analysis workflows.
+
+**Best used when:**
+- Finding all usages of a function or variable
+- Locating specific log statements or debug markers
+- Discovering patterns across the codebase
+- Understanding how a feature is implemented across files
+
+**Example use cases:**
+- "Find all occurrences of 'widget.height' in the Flutter project"
+- "Search for '🎯 \[BUILDER\]' logs in .dart files"
+- "Find all files that call 'HeroBannerWidget'"
+
+#### 6. `rollback_file`
+**Purpose:** Restores a file to a previous state from the automated backup system.
+**Input:**
+- `filePath` (required): Absolute path.
+- `steps` (optional): Number of versions to go back (1-5, default: 1).
+**What it does:** Reverts the file to the state it was in before the last 1-5 modifications.
+
+### Write Tools (v2.2.0 Mandatory Workflow)
+
+All write tools follow a **Two-Phase Workflow**:
+1. **Phase 1 (Preview)**: Call without a token to get a unified `diff` and a `confirmationToken`.
+2. **Phase 2 (Apply)**: Call with `confirmationToken` and `confirm: true` to apply the changes.
+
+**Important Notes (v2.2.0):**
+- ✅ **Windows CRLF Support**: Fully resolved. All operations work correctly on Windows files with CRLF line endings.
+- ✅ **Parameter Brace Handling**: Methods with braces in parameters (e.g., `{int? cart}`) are now handled correctly.
+
+#### 7. `write_file_surgical`
+**Purpose:** Replace the full source code of a named symbol in a file.
+
+**Input:**
+- `filePath` (required): Absolute path to the file to modify.
+- `symbolName` (required): Name of the symbol to replace.
+- `newContent` (required): Complete replacement code (signature + body).
+- `confirmationToken` (optional): Token from Phase 1.
+- `confirm` (optional): Set to `true` to apply.
+- `className` (optional): Scope the symbol to a specific class.
+
+**What it does:**
+- Locates the symbol via Tree-sitter WASM parsing.
+- Replaces only that symbol's code, preserving all other file contents.
+- Returns a unified diff showing exactly what changed.
+- Validates the result is syntactically valid before writing.
+
+**Best used when:** You need to modify a specific function or method without touching the rest of the file.
+
+#### 8. `insert_symbol`
+**Purpose:** Insert new code at a precise location relative to an existing symbol.
+
+**Input:**
+- `filePath` (required): Absolute path to the file.
+- `code` (required): The new code to insert.
+- `anchorSymbol` (optional): Symbol name to position relative to. If omitted, inserts at end of file.
+- `position` (optional): `"before"`, `"after"`, `"inside_start"`, `"inside_end"`. Defaults to `"after"`.
+- `confirmationToken`, `confirm` (optional): Standard Phase 2 parameters.
+
+**What it does:**
+- Finds the anchor symbol and inserts new code at the specified position.
+- Automatically matches the surrounding indentation style.
+- `inside_start` and `inside_end` insert as members inside a class or interface.
+
+**Best used when:** Adding new methods to a class or new functions to a module.
+
+#### 9. `rename_symbol`
+**Purpose:** Rename a symbol across an entire repository.
+
+**Input:**
+- `filePath` (required): File where the symbol is defined.
+- `oldName` (required): Current name.
+- `newName` (required): New name.
+- `rootDir` (optional): Repository root. Auto-detected if omitted.
+- `confirmationToken`, `confirm` (optional): Standard Phase 2 parameters.
+
+**What it does:**
+- Renames the symbol definition in the source file.
+- Finds all dependent files using import analysis.
+- Renames all references in dependent files using whole-word replacement.
+- Returns a multi-file diff showing all changes.
+- Rolls back all changes if any file write fails.
+
+**Best used when:** Refactoring a class, function, or method name that is used across multiple files.
+
+#### 10. `remove_symbol`
+**Purpose:** Safely remove a symbol from a file.
+
+**Input:**
+- `filePath` (required): Absolute path.
+- `symbolName` (required): Symbol to remove.
+- `force` (optional): If true, skip dependency check. Defaults to false.
+- `confirmationToken`, `confirm` (optional): Standard Phase 2 parameters.
+
+**What it does:**
+- Checks if other files reference the symbol (unless `force: true`).
+- If dependents exist, refuses to remove and reports which files use it.
+- If safe, removes the symbol's code and cleans up whitespace.
+
+**Best used when:** Cleaning up deprecated functions or unused code.
+
+## Recommended Workflow
+
+1. **Start with `get_semantic_repo_map`** to understand the project structure.
+2. **Use `read_file_surgical`** with a symbol name. Use suggestions if the symbol is missing.
+3. **Before modifying, run `analyze_impact`** to know the blast radius.
+4. **Phase 1: Preview Edit** → Call write tools to get a `diff` and `confirmationToken`.
+5. **Phase 2: Apply Edit** → Verify the diff, then call with the token and `confirm: true`.
+6. **Recovery** → Use `rollback_file` if needed.
+
+## Technical Details
+
+- **Transport:** stdio (JSON-RPC over stdin/stdout)
+- **Runtime:** Node.js >= 18
+- **AST Engines:** web-tree-sitter@0.25.1 (WASM) for all languages
+- **Language Grammars:** tree-sitter-wasms@0.1.13 (ABI v15)
+- **Ignore Engine:** `ignore` npm package (full .gitignore spec support)
+- **Supported languages:** TypeScript, JavaScript (all variants), PHP, Dart, Python
+- **Safety features:** Mandatory two-phase confirmation, rolling 5-version backups (`.mcp-backups/`), fuzzy symbol suggestions, dependency tracking, surgical restoration.
+- **Portability:** 100% WASM - no native dependencies, works on all platforms

package/package.json

@@ -1,57 +1,59 @@
-{
-  "name": "mcp-code-context",
-  "version": "2.5.1",
-  "description": "Powerful MCP server for LLM-ready semantic code context and surgical AST-aware editing. Supports TypeScript, JavaScript, PHP, Dart, and Python.",
-  "type": "module",
-  "main": "dist/src/index.js",
-  "bin": {
-    "mcp-code-context": "dist/src/index.js"
-  },
-  "scripts": {
-    "build": "tsc",
-    "start": "node dist/src/index.js",
-    "dev": "tsc && node dist/src/index.js",
-    "test": "npm run build && node dist/tests/test-dart.js && node dist/tests/test-php.js && node dist/tests/writers/test-write-smoke.js && node dist/tests/test-new-tools.js && node dist/tests/test-backup-system.js && node dist/tests/test-rename-limitations.js",
-    "clean": "rimraf dist",
-    "rebuild": "npm run clean && npm run build"
-  },
-  "keywords": [
-    "mcp",
-    "model-context-protocol",
-    "semantic-compression",
-    "llm",
-    "code-analysis",
-    "ast",
-    "repository-map",
-    "claude",
-    "cursor",
-    "windsurf",
-    "copilot",
-    "amazon-q",
-    "code-context",
-    "typescript",
-    "php",
-    "dart",
-    "python"
-  ],
-  "author": "",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/achatainga/mcp-code-context.git"
-  },
-  "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.12.0",
-    "ignore": "^6.0.2",
-    "php-parser": "^3.5.1",
-    "ts-morph": "^24.0.0",
-    "typescript": "^5.7.0"
-  },
-  "devDependencies": {
-    "@types/node": "^22.10.0",
-    "rimraf": "^6.0.1"
-  },
-  "engines": {
-    "node": ">=18.0.0"
-  }
-}
+{
+  "name": "mcp-code-context",
+  "version": "3.0.4",
+  "description": "Powerful MCP server with Tree-sitter WASM parsers for 100% AST accuracy. Zero native dependencies. Supports TypeScript, JavaScript, PHP, Dart, and Python.",
+  "type": "module",
+  "main": "dist/src/index.js",
+  "bin": {
+    "mcp-code-context": "dist/src/index.js"
+  },
+  "scripts": {
+    "build": "tsc",
+    "build:tests": "tsc -p tsconfig.tests.json",
+    "start": "node dist/index.js",
+    "dev": "npm run build && node dist/index.js",
+    "test": "npm run build && npm run build:tests && node dist-tests/tests/test-wasm-parsers.js",
+    "clean": "rimraf dist dist-tests",
+    "rebuild": "npm run clean && npm run build",
+    "prepublishOnly": "npm run rebuild"
+  },
+  "keywords": [
+    "mcp",
+    "model-context-protocol",
+    "semantic-compression",
+    "llm",
+    "code-analysis",
+    "ast",
+    "repository-map",
+    "claude",
+    "cursor",
+    "windsurf",
+    "copilot",
+    "amazon-q",
+    "code-context",
+    "typescript",
+    "php",
+    "dart",
+    "python"
+  ],
+  "author": "",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/achatainga/mcp-code-context.git"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.12.0",
+    "ignore": "^6.0.2",
+    "tree-sitter-wasms": "^0.1.13",
+    "web-tree-sitter": "^0.25.1"
+  },
+  "devDependencies": {
+    "@types/node": "^22.10.0",
+    "rimraf": "^6.0.1",
+    "typescript": "^5.7.0"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  }
+}