Log inSubmit server
Code Index logo

Code Index

Indexes source code in SQLite and exposes symbol search, file access, and call-graph analysis through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Code Index

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": {
    "code-index": {
      "command": "npx",
      "args": [
        "-y",
        "@regsorm/code-index-mcp"
      ],
      "env": {
        "CODE_INDEX_HOME": "YOUR_VALUE_HERE"
      }
    }
  }
}

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

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

code-index MCP server parses repositories into a SQLite index using Rust and tree-sitter, then exposes code navigation and analysis through MCP. It supports general source-code indexing and an extended build for 1C:Enterprise 8.3 exports from Configurator or 1C:EDT. Tools cover symbol and text search, function and class retrieval, file inspection, imports, callers, callees, and call paths. Reach for it when an agent needs structured answers about a codebase without repeatedly scanning entire files.

Use cases

  • Search a repository for functions, classes, symbols, or text
  • Trace callers and callees across a codebase
  • Find a bounded call path between two functions
  • Inspect 1C object relationships and event handlers
  • Read selected file ranges without loading whole files

Key features

  • SQLite-backed source-code indexing
  • Function, class, symbol, text, and regex search
  • Caller, callee, call-path, and call-tree analysis
  • Bounded file listing, metadata, and content access
  • 1C:Enterprise metadata and BSL analysis
  • Multi-repository access through repository aliases

Tools31

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

Self-reported~1.6k 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 1d ago

Recent health check succeeded.

25/27 checks healthy over the last 93d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @regsorm/code-index-mcp (npm)

Adoption & maintenance

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

GitHub stars161Stargazers on the source repository.
npm downloads5.1kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed31Callable tools this server registers over MCP.
Directory activity9 viewsConfig copies, upvotes, and views on AllMCPs.

How Code Index works

What code-index does

code-index turns a repository into a searchable index for AI agents. It stores symbols, source text, relationships, and file metadata in SQLite, then serves query results over the Model Context Protocol. The index includes functions, classes, variables, imports, file summaries, and call relationships. Search can cover function names, documentation, bodies, classes, symbols, text files, or code-file contents.

The project also has an extended build for 1C:Enterprise 8.3 exports. It can analyze metadata objects, forms, event handlers, subscriptions, data links, register writers, object profiles, references, and BSL procedure relationships. The core package is intended for repositories without the 1C-specific enrichment layer.

How it works

A background daemon builds and updates the index while the MCP serving process reads it. The server can expose one index across multiple sessions and repositories; each tool call accepts a repository alias. Initial indexing parses the source tree, while later changes are picked up incrementally. The indexer uses file metadata to check an existing index before starting work.

The server supports stdio, where an MCP client launches a process for a session, and HTTP through an embedded endpoint. The default HTTP listener binds to 127.0.0.1 and uses /mcp; network-facing deployments require allowed host names. HTTP is useful when several sessions or projects should share one server process.

Call-graph tools provide callers, callees, shortest paths, and bounded call trees. Data-oriented tools provide related object references and paths through 1C metadata links. File-reading tools include line ranges and response limits, while listing and grep tools support path, language, glob, regex, and context filters where applicable.

Setup and configuration

On Windows, the project provides an installation script that downloads the latest release, creates a settings-file template, and can configure user-level autostart. Release archives are available for Windows, Linux, and macOS ARM64. The npm package installs a platform-specific binary and can start the server with:

Terminal
npm install -g @regsorm/code-index-mcp
npx @regsorm/code-index-mcp serve --path /path/to/repository

The npm wrapper contains the build without 1C support. Its serving process requires the background daemon to be running with npx @regsorm/code-index-mcp daemon run, and CODE_INDEX_HOME must identify the installation or data location. Source builds require Rust 1.77 or newer. The 1C-enabled binary is built separately with the bsl-indexer package and its enrichment feature.

A stdio client configuration can launch serve directly. For HTTP, configure the MCP client with http://127.0.0.1:8011/mcp unless the listener port or host has been changed. When binding beyond loopback, configure allowed hosts through the server settings or CODE_INDEX_ALLOWED_HOSTS.

Tools and capabilities

  • Search functions, classes, symbols, text files, and code bodies with full-text, substring, or regular-expression queries.
  • Retrieve exact functions and classes, with case-insensitive fallback and similar-name suggestions when available.
  • Inspect file listings, file metadata, bounded file contents, imports, summaries, and index statistics.
  • Traverse callers, callees, shortest call paths, and bounded call trees across indexed code.
  • Query 1C forms, event subscriptions, object structures, data links, register writers, profiles, and references with the 1C-enabled build.
  • Check server health and the connected repositories.

Limitations and notes

The serving process reads the index; the background daemon is responsible for building it. If the daemon is offline, tools return a daemon_offline condition. File-reading responses have size limits: the soft cap is 5,000 lines or 500 KB, with a 2 MB hard cap. File listings default to 500 results and report truncation when more matches exist.

Large code files can be marked as oversized, and large 1C templates may remain outside the content index while still appearing as discoverable template records. Call-tree, call-path, and data-path queries are bounded by depth or node limits, so results can be incomplete when those limits are reached. The optional code-index-guard hook can direct Claude Code and Codex CLI toward indexed reads instead of ordinary file operations.

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 Code Index

code-index is an MCP server that connects AI clients to indexed code repositories through a Rust and SQLite index. Its main tools search functions, classes, symbols, text, and code bodies; retrieve files and definitions; inspect imports; and trace callers, callees, call paths, and call trees. An extended build also analyzes 1C:Enterprise projects.

Install the npm package globally with `npm install -g @regsorm/code-index-mcp`, then run `npx @regsorm/code-index-mcp serve --path /path/to/repository`. Start the background daemon separately with `npx @regsorm/code-index-mcp daemon run` and set `CODE_INDEX_HOME`. Windows also has a release installer script.

Yes, code-index works with Cursor through MCP. Configure Cursor with either the stdio command that launches `npx @regsorm/code-index-mcp serve --path .` or the HTTP endpoint `http://127.0.0.1:8011/mcp`. The background indexing daemon must be running for the tools to answer.

Yes, the 1C-enabled `bsl-indexer` build analyzes 1C:Enterprise 8.3 exports from Configurator and 1C:EDT. It adds tools for BSL procedures, metadata objects, forms, event subscriptions, data links, register writers, object profiles, and references. The npm package provides the build without 1C support.

Set the client URL to `http://127.0.0.1:8011/mcp` and use the HTTP MCP transport. The embedded server listens on loopback by default, so no separate web server is needed. If you expose it beyond loopback, configure the permitted host names with server settings or `CODE_INDEX_ALLOWED_HOSTS`.

Related MCP servers

All in Databases 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 PreviewCode Index AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/code-index?style=directory)](https://allmcps.com/mcp/code-index)
HTML Embed
<a href="https://allmcps.com/mcp/code-index"><img src="https://allmcps.com/api/badge/code-index?style=directory" alt="Code Index on AllMCPs" /></a>