code index mcp

Code Index MCP is a Model Context Protocol server that enables large language models (LLMs) to index, search, and analyze code in project directories.

Features

• Index and navigate project file structures
• Search for specific patterns in code
• Get detailed file summaries
• Analyze code structure and complexity
• Support for multiple programming languages
• Persistent storage of project settings

Installation

This project uses uv for environment management and dependency installation.

1. Ensure you have Python 3.10 or later installed
2. Install uv (recommended):

# Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

# Clone the repository
git clone https://github.com/your-username/code-index-mcp.git

Usage

Running the Server Directly

# Run directly with uv - no additional dependency installation needed
uv run run.py

UV will automatically handle all dependency installations based on the project's configuration.

Integrating with Claude Desktop

You can easily integrate Code Index MCP with Claude Desktop:

1. Ensure you have UV installed (see installation section above)

2. Find or create the Claude Desktop configuration file:

3. Windows: %APPDATA%Claudeclaude_desktop_config.json

4. macOS/Linux: ~/Library/Application Support/Claude/claude_desktop_config.json
5. Add the following configuration (replace with your actual path):

For Windows:

{
  "mcpServers": {
    "code-indexer": {
      "command": "uv",
      "args": [
         "--directory",
         "C:Usersusernamepathtocode-index-mcp",
         "run",
         "run.py"
       ]
    }
  }
}

For macOS/Linux:

{
  "mcpServers": {
    "code-indexer": {
      "command": "uv",
      "args": [
         "--directory",
         "/home/username/path/to/code-index-mcp",
         "run",
         "run.py"
       ]
    }
  }
}

Note: The --directory option is important as it ensures uv runs in the correct project directory and can properly load all dependencies. 4. Restart Claude Desktop to use Code Indexer for analyzing code projects

No manual dependency installation is required - UV will automatically handle all dependencies when running the server.

Basic Workflow

1. Set Project Path (required first step):

2. When using for the first time, you must set the project path to analyze

3. Through Claude command: "I need to analyze a project, help me set up the project path"
4. Provide the complete project directory path

5. Code Search:

6. Search for specific keywords or patterns: "Search for 'function name' in the project"

7. Filter by file type: "Search for 'import' in all .py files"

8. File Analysis:

9. Analyze specific files: "Analyze the file src/main.py"

10. Get file summaries: "Give me a list of functions in utils/helpers.js"

11. Project Navigation:

12. View project structure: "Show me the structure of this project"

13. Find files matching specific patterns: "Find all test_*.py files"

Technical Details

Persistent Storage

All index and settings data are stored in the .code_indexer folder within the project directory:

• config.json: Project configuration information
• file_index.pickle: File index data
• content_cache.pickle: File content cache

This ensures that the entire project does not need to be re-indexed each time it's used.

Dependency Management with UV

Code Index MCP uses UV for dependency management, which provides several advantages:

• Automatic dependency resolution based on project requirements
• Faster package installation and environment setup
• Consistent dependency versions via the lock file

Supported File Types

The following file types are currently supported for indexing and analysis:

• Python (.py)
• JavaScript/TypeScript (.js, .ts, .jsx, .tsx)
• Java (.java)
• C/C++ (.c, .cpp, .h, .hpp)
• C# (.cs)
• Go (.go)
• Ruby (.rb)
• PHP (.php)
• Swift (.swift)
• Kotlin (.kt)
• Rust (.rs)
• Scala (.scala)
• Shell (.sh, .bash)
• HTML/CSS (.html, .css, .scss)
• Markdown (.md)
• JSON (.json)
• XML (.xml)
• YAML (.yml, .yaml)

Security Considerations

• File path validation prevents directory traversal attacks
• Absolute path access is not allowed
• Project path must be explicitly set, with no default value
• The .code_indexer folder includes a .gitignore file to prevent indexing data from being committed

Contributing

Contributions via issues or pull requests to add new features or fix bugs are welcome.

For documentation in Chinese, please see README_zh.md.