officialalexeev

Anyindex MCP — AI skill for Claude Code

AI community

Local MCP server for semantic code search.

How to install Anyindex MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open officialalexeev/anyindex-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Anyindex MCP does

Local MCP server for semantic code search. AST-aware chunking with tree-sitter, offline ONNX embeddings, hybrid vector + BM25 (RRF) ranking, one SQLite file. No API keys or cloud. Semantic code search for Claude Code, Cursor, opencode and AI coding agents.

Alternatives in AI

Jcodemunch MCP — Cut AI token costs 95%+ on code exploration 2.6k ★
Azure OpenAI .net — GPT-4, embeddings, DALL-E, and Whisper client 1.8k ★
Empryo — Empryo issue tracker + SoulForge (v2) 1.1k ★

README

anyindex-mcp

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![Node](https://img.shields.io/badge/node-%5E22.19%20%7C%20%3E%3D24.0.0-lightgreen.svg)](https://nodejs.org)

Fully local MCP server for indexing a codebase and answering semantic search queries about it. No external API calls, no telemetry, no server process to run.

AST-aware chunking via tree-sitter — chunks follow function and class boundaries, never cut mid-statement
Offline embeddings via ONNX in-process; after the first download the model works with no network
Hybrid search — vector + BM25 fused with RRF
One SQLite file in the project, plus an FTS5 index
Works on Windows without Visual Studio Build Tools — see Platform

Quickstart

Wire it into a client — nothing to install, see [Client configuration](#client-configuration):

npx --package anyindex-mcp anyindex-mcp-server

Build the index once from your project, so the first search has something to read:

npx --package anyindex-mcp anyindex-mcp reindex --root /path/to/project
npx --package anyindex-mcp anyindex-mcp search --root /path/to/project "user authentication flow"

After a global `npm install -g anyindex-mcp` the `npx --package …` prefix drops away and the commands are just `anyindex-mcp reindex` and `anyindex-mcp search`.

A second `reindex` only touches changed files. To keep the index fresh while you edit, pass `--watch` to the **server**, not to the CLI:

npx --package anyindex-mcp anyindex-mcp-server --watch

To work on anyindex-mcp itself, from a checkout:

npm install
npm run build
npm run probe      # environment check, prints ms/chunk

Requirements

Node `^22.19.0 || >=24.0.0`. Node 23.x does not qualify at any patch level.

Embedding dominates the wall clock: plan against ~1 s/chunk on 4 cores, not the optimistic `probe` figure. If a run stalls, it is memory pressure — free RAM and retry. Measured numbers