Log inSubmit server
Codeindex logo

Codeindex

Indexes local codebases for symbol lookup, dependency tracing, refactoring plans, file reading, and 22 static analyses over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Codeindex

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "codeindex": {
      "command": "npx",
      "args": [
        "-y",
        "@munhq/codeindex"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @munhq/codeindex

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 15d ago.

Overview

The codeindex MCP server gives AI coding agents structural access to a local workspace through symbol, caller, import, dependency, and file-reading tools. It parses more than 40 languages with tree-sitter, then builds searchable indexes and a dependency graph that can be shared by sessions through a workspace daemon. Use it when an agent needs targeted code navigation, change-impact analysis, refactoring plans, or repository-wide checks without reading every file. It runs over stdio and can be installed through npm, a shell installer, a compiled binary, or Docker.

Use cases

  • Find callers before changing a shared function
  • Trace imports and reverse dependencies across a workspace
  • Generate a refactoring plan with blast-radius details
  • Run repository analyses for cycles, dead code, security patterns, and coverage gaps

Key features

  • Tree-sitter parsing for 40+ languages
  • Symbol, word, trigram, and full-text lookup
  • Caller, import, and transitive impact analysis
  • Shared workspace daemon with file watching
  • 22 repository analysis modes
  • Focused file and symbol source reading

Tools16

What Codeindex lets your agent do. Expand a tool for its parameters.

Self-reported~288 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @munhq/codeindex (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads765Package downloads in the last 30 days.
Last commit14d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed16Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Codeindex works

What codeindex does

The codeindex MCP server indexes a local software workspace and exposes code-navigation data to MCP clients. It supports more than 40 languages, including Rust, Python, TypeScript, Go, Java, C and C++, Ruby, Kotlin, Swift, SQL, JSON, YAML, Dockerfile, Markdown, and others. Parsing uses tree-sitter, while separate trigram and inverted-word indexes support text and identifier lookup.

The server is designed for questions about code structure rather than only file contents. It can locate definitions, show a file outline, identify callers, trace imports in both directions, calculate a transitive change impact, and produce a refactoring plan for a symbol or file. It can also return selected file or symbol source, list recently changed files, and report index status.

How it works

An MCP client communicates with a local relay over stdio. By default, a workspace daemon maintains the shared index, dependency graph, file watcher, and persisted snapshot. Multiple sessions connected to the same repository can therefore use one indexed representation instead of building independent copies. The daemon can be disabled with the --no-daemon option.

The analyze tool runs one of 22 named analyses. These cover areas such as security patterns, dead code, test coverage, architecture, dependency cycles, coupling, duplication, type drift, migration parity, hardcoded literals, dependency inventory, and database or call-cost concerns. The health analysis combines results into an index-health report.

Setup and configuration

Node.js 18 or newer is the shortest installation path. The npm package is @munhq/codeindex; an MCP client can launch it with npx -y @munhq/codeindex. The repository also provides an install script that installs the prebuilt binary, skill, and MCP registration, plus a source-build path using Zig. Docker is available when the server should run as an image; the documented example mounts the workspace at /workspace as read-only.

The executable runs as an MCP server with codeindex --mcp. It can be registered directly with Claude Code or configured in an MCP client using the command and args fields. The project documentation warns against registering both the Claude Code plugin and a separate direct server for the same workspace, because that creates duplicate server processes and snapshots.

Tools and capabilities

The codeindex MCP server provides these tools:

  • status, index_workspace, and get_tree for index state, workspace indexing, and file metadata.
  • search, find_word, and find_symbol for full-text, identifier, and definition lookup.
  • find_callers, get_imports, get_imported_by, and get_change_impact for references and dependency tracing.
  • get_outline, read_file, and read_symbol for focused source inspection.
  • plan_change for definitions, callers, file role, literals, and transitive impact.
  • get_hot_files for recently changed files.
  • analyze for the repository analyses described above.

Limitations and notes

Caller matching is name-based, so a same-named definition elsewhere may also appear in the results. The available structural information depends on the indexed workspace and the supported language parsers. The Docker example treats the workspace as read-only, while normal local operation maintains an index, watcher, and persisted snapshot outside the source tree as configured by the server. No API key is required for the documented npm quickstart.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Codeindex

codeindex is an MCP server that connects AI coding agents to a locally indexed code workspace. Its main tools search files, find symbols and callers, inspect imports, read files or symbols, calculate change impact, create refactoring plans, and run 22 code analyses across more than 40 supported languages.

Install it with Node.js 18 or newer by registering `npx -y @munhq/codeindex` as an MCP server. You can also use the repository’s shell installer, build the binary with Zig, or run the published Docker image with the workspace mounted at `/workspace`.

Yes, codeindex works with Cursor through its standard MCP configuration. Add a server named `codeindex` with `npx` as the command and `-y`, `@munhq/codeindex` as the arguments, or use the repository’s Cursor installation link.

Use the `analyze` MCP tool and select one of its 22 analysis modes. Available checks include security patterns, dead code, test coverage, architecture, cycles, duplication, dependency inventory, literal scanning, migration parity, call cost, and a combined `health` report.

Yes, the `get_change_impact` tool calculates a transitive dependency blast radius for a file, while `plan_change` combines impact information with definitions, callers, file role, and literals to inspect during a refactor.

Related MCP servers

All in Biology & Bioinformatics All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCodeindex AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/codeindex?style=directory)](https://allmcps.com/mcp/codeindex)
HTML Embed
<a href="https://allmcps.com/mcp/codeindex"><img src="https://allmcps.com/api/badge/codeindex?style=directory" alt="Codeindex on AllMCPs" /></a>