Codeix

What the Codeix MCP server does

The Codeix MCP server gives AI coding agents a structured view of one or more local codebases. Instead of returning only matching text, its index records files, symbols, signatures, line ranges, kinds, and parent relationships. Agents can use this information to locate definitions, understand project layout, inspect class or module members, and trace calls and references.

The index is stored in a .codeindex directory containing a manifest plus JSONL files for source files, symbols, and text entries. Because these files are plain and portable, they can be inspected with standard JSON tools and committed alongside a repository. Dependency indexes can also be discovered and mounted when the server queries a project.

Supported parsing includes Python, Rust, JavaScript, TypeScript, Go, Java, C, C++, Ruby, C#, and Markdown. HTML, Vue, Svelte, and Astro files can expose embedded JavaScript or TypeScript for indexing. Markdown headings become section symbols, while fenced code blocks are indexed as text entries.

How it works

Run codeix build to parse source files and write the index. Running codeix or codeix serve starts the MCP server; the default mode watches for changes, while serve --no-watch disables watching. A root directory can be supplied with -r, and directory discovery treats each folder containing .git/ as a separate project.

Queries run against the local index. The search tool combines symbol, file, and text search with FTS5 and BM25 ranking. Scope, symbol kind, path, and project filters narrow results. Text scope is intended for comments, docstrings, and string literals, while symbol-oriented results include structural metadata.

Setup and configuration

Install the same standalone binary through npm or npx, pip or uvx, Cargo, Homebrew, or a source build. Examples include npx codeix, uvx codeix, cargo install codeix, and brew install codeix. The project states that the binary has no runtime dependencies.

Add the executable to an MCP client configuration using a stdio command such as:

{
  "mcpServers": {
    "codeix": {
      "command": "codeix"
    }
  }
}

The documented examples are Claude Desktop and Cursor. Codeix is local-only and does not require network access or API keys. Build an index before querying a new project, unless a committed .codeindex is already available.

Tools and capabilities

The Codeix MCP server exposes seven tools:

• explore returns project metadata, subprojects, and files grouped by directory.
• search performs filtered, ranked searches across symbols, files, and indexed text.
• get_file_symbols lists symbols found in a selected file.
• get_children returns the members or nested symbols of a class or module.
• get_callers finds locations that call or reference a symbol.
• get_callees lists symbols called by a function or method.
• flush_index writes pending index changes to disk.

Limitations and notes

Language support depends on compile-time feature flags, although the listed language features are enabled by default. The server indexes supported source formats and does not provide a general-purpose semantic analysis claim beyond the listed navigation and search operations. It is designed for local repositories and offline use. Its license is dual MIT OR Apache-2.0.