johnhuang316/code-index-mcp

Intelligent code indexing and analysis for Large Language Models
Transform how AI understands your codebase with advanced search, analysis, and navigation capabilities.
## Overview
Code Index MCP is a Model Context Protocol server that bridges the gap between AI models and complex codebases. It provides intelligent indexing, advanced search capabilities, and detailed code analysis to help AI assistants understand and navigate your projects effectively.
Perfect for: Code review, refactoring, documentation generation, debugging assistance, and architectural analysis.
## Quick Start
### 🚀 Recommended Setup (Most Users)
The easiest way to get started with any MCP-compatible application:
Prerequisites: Python 3.10+ and uv
1. Add to your MCP configuration (e.g., claudedesktopconfig.json or ~/.claude.json):
json
"mcpServers": {
"code-index": {
"command": "uvx",
"args": ["code-index-mcp"]
> Optional: append --project-path /absolute/path/to/repo to the args array so the server
> initializes with that repository automatically (equivalent to calling setprojectpath
> after startup).
2. Restart your application – uvx automatically handles installation and execution
3. Start using (give these prompts to your AI assistant):
Set the project path to /Users/dev/my-react-app
Find all TypeScript files in this project
Search for "authentication" functions
Analyze the main App.tsx file
If you launch with --project-path, you can skip the first command above - the server already
knows the project location.
### Codex CLI Configuration
If you are using Anthropic's Codex CLI, add the server to ~/.codex/config.toml.
On Windows the file lives at C:\Users\ \.codex\config.toml:
toml
[mcpservers.code-index]
type = "stdio"
command = "uvx"
args = ["code-index-mcp"]
> You can append --project-path C:/absolute/path/to/repo to the args list to set the project
> automatically on startup (same effect as running the setprojectpath tool).
On Windows, uvx needs the standard profile directories to be present.
Keep the environment override in the same block so the MCP starts reliably:
toml
env = {
HOME = "C:\\Users\\ ",
APPDATA = "C:\\Users\\ \\AppData\\Roaming",
LOCALAPPDATA = "C:\\Users\\ \\AppData\\Local",
SystemRoot = "C:\\Windows"
Linux and macOS already expose the required XDG paths and HOME, so you can usually omit the env
table there.
Add overrides only if you run the CLI inside a restricted container.
### FastMCP & Discovery Manifests
Run fastmcp run fastmcp.json to launch the server via FastMCP with
the correct source entrypoint and dependency metadata. Pass --project-path (or call the
setprojectpath tool after startup) so the index boots against the right repository.
Serve or copy .well-known/mcp.json to share a standards-compliant MCP manifest. Clients that
support the .well-known convention (e.g., Claude Desktop, Codex CLI) can import this file
directly instead of crafting configs manually.
Publish .well-known/mcp.llmfeed.json when you want to expose the richer LLM Feed metadata.
It references the same code-index server definition plus documentation/source links, which
helps registries present descriptions, tags, and capabilities automatically.
When sharing the manifests, remind consumers to supply --project-path (or to call