Code Index MCP for VS Code: Setup & Config

What you can do with Code Index in VS Code

Use quick file indexing and opt-in deep syntax analysis to help assistants navigate larger repositories.

• Locate files by glob before inspecting them.
• Summarize imports, functions, and complexity after deep indexing.
• Explore an unfamiliar repository during a code review.

Before you start: Code Index in VS Code

• Python 3.10+
• uv / uvx
• A project directory to index
• A native search utility for regex mode

Call set_project_path after launch or use the documented --project-path option. File watching refreshes the shallow index; build_deep_index is required for symbol summaries. Windows clients may need the profile-directory environment overrides described in the README.

Code Index VS Code configuration

1. Choose VS Code configuration scope

   For Code Index MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Code Index MCP to VS Code

   Use the code-index-mcp entry below in servers. Keep Code Index MCP's documented stdio connection fields and your other VS Code entries.

3. Check Code Index MCP in VS Code

   Code Index MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "code-index-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "code-index-mcp"
      ],
      "env": {}
    }
  }
}

Code Index tools available to VS Code

Code Index's stored tool list documents 13 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

set_project_path

Look for set_project_path among VS Code's agent-mode tools after starting Code Index through the MCP controls.

refresh_index

Look for refresh_index among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Rebuild the shallow file index.

build_deep_index

Look for build_deep_index among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Build symbol metadata needed for deep analysis.

get_settings_info

Look for get_settings_info among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Inspect project configuration and indexing status.

search_code_advanced

Look for search_code_advanced among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Search code with filters, pagination, and optional fuzzy or regex matching.

find_files

Look for find_files among VS Code's agent-mode tools after starting Code Index through the MCP controls.

get_file_summary

Look for get_file_summary among VS Code's agent-mode tools after starting Code Index through the MCP controls.

get_file_watcher_status

Look for get_file_watcher_status among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Inspect whether filesystem monitoring is active.

configure_file_watcher

Look for configure_file_watcher among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Configure automatic refresh and watcher behavior.

create_temp_directory

Look for create_temp_directory among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Prepare a storage directory for index data.

check_temp_directory

Look for check_temp_directory among VS Code's agent-mode tools after starting Code Index through the MCP controls.

clear_settings

Look for clear_settings among VS Code's agent-mode tools after starting Code Index through the MCP controls.

refresh_search_tools

Look for refresh_search_tools among VS Code's agent-mode tools after starting Code Index through the MCP controls.

Code Index: full stored tool descriptions

Troubleshooting Code Index in VS Code

• Make uvx code-index-mcp (from uv, for Python tools) available in the workspace, container, or remote environment hosting Code Index MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
• Code Index MCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Deep summaries require build_deep_index first.
• Known limitation: Languages outside the specialized set get basic fallback indexing.
• Known limitation: Regex search requires an installed native search utility.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions