Semdex
A local MCP server that parses codebases into semantic chunks, indexes them in SQLite with vector embeddings, and exposes MCP tools for LLM agents to query.
README
Semdex
A local MCP server that gives AI coding assistants structured, queryable intelligence about a codebase.
Overview
Semdex (semantic + index) is a local MCP server that parses codebases into semantic chunks (functions, classes, interfaces), indexes them in SQLite with vector embeddings, and exposes MCP tools for LLM agents to query.
Think of it as an LSP, but for AI — instead of "go to definition" for humans, it's "find all relevant code" for an LLM.
Why Semdex?
- Context windows are limited. LLMs can't fit an entire codebase in context. Semdex finds exactly the relevant code and feeds only that to the model.
- Structure-aware, not grep. Traditional search matches text; Semdex understands code structure — functions, classes, methods, interfaces — and their relationships.
- Runs locally. No cloud dependencies, no API keys, no data leaving your machine. Works offline.
- Editor-agnostic. Speaks MCP, the standard protocol for AI tool integration. Works with any MCP-compatible client.
Status
⚠️ Early Development — This project is in the design and planning phase. No source code has been written yet. See CONTRIBUTING.md if you'd like to help build it.
Technology Stack
| Layer | Choice | Constraint |
|---|---|---|
| Runtime | Node.js 22 LTS | Do NOT use APIs that require 23+ |
| Language | TypeScript 5.x | Strict mode, no any without justification |
| CLI | Commander.js | One entry point: src/cli.ts → sdx binary |
| AST | Tree-sitter WASM | NOT native bindings. Language.load() from .wasm files |
| DB | better-sqlite3 + sqlite-vec | sqliteVec.load(db) — NOT node:sqlite (23.5+) |
| Hashing | hash-wasm | xxhash3() for content hashing |
| Embedding | Transformers.js v3.x | Xenova/all-MiniLM-L6-v2, q8 quantized, max 256 tokens input |
| Watcher | Chokidar | awaitWriteFinish: true, ignore node_modules |
| Telemetry | OpenTelemetry JS | Custom FileSpanExporter, manual instrumentation only |
| MCP SDK | @modelcontextprotocol/sdk | v1.29.0 (@release-1.29.0). Do NOT use v2 alpha |
| Testing | Vitest | In-memory SQLite for DB tests, no external deps |
Architecture
src/
├── cli.ts # Commander.js entry point
├── server.ts # McpServer + tool registration
├── indexer/
│ ├── parser.ts # Tree-sitter WASM → AST
│ ├── chunker.ts # AST → canonical semantic nodes
│ ├── hasher.ts # XXH3 content hashing
│ └── embedder.ts # Transformers.js pipeline
├── db/
│ ├── connection.ts # better-sqlite3 + sqlite-vec
│ ├── schema.ts # Migration framework (PRAGMA user_version)
│ └── queries.ts # Typed SQL query builders
├── tools/
│ ├── symbol.ts # symbol.find, symbol.callers
│ ├── search.ts # search.semantic, search.lexical
│ ├── repo.ts # repo.manifest, repo.architecture
│ └── index.ts # index.status, code.read
└── telemetry/
├── tracer.ts # OpenTelemetry setup
└── file-exporter.ts # Custom FileSpanExporter (~50 lines)
Getting Started
📝 Coming soon. Setup instructions will be added once initial source code is written.
Planned workflow:
sdx init # Initialize index in current repo
sdx index --dry-run # Preview what would be indexed
sdx serve # Start MCP server (stdio transport)
Key Commands
npm run build # tsc
npm run dev # tsx src/cli.ts
npm test # vitest
npm run lint # eslint src/
npm run typecheck # tsc --noEmit
sdx init # Initialize index in current repo
sdx index --dry-run # Preview what would be indexed
sdx serve # Start MCP server (stdio transport)
sdx bench # Run benchmarks
sdx bench --sla # Check against SLA targets
Design Principles
- Never fail silently. Every degraded mode must log a warning and produce useful results.
- Lexical fallback beats an error. If embeddings fail, FTS5 is better than nothing.
- Partial index beats no index. One broken file should never block the whole repo.
- Content-addressable everything. Never recompute what hasn't changed.
- Explicit over implicit. Schema migrations, model switches — all opt-in, never automatic.
- Local only. No cloud, no telemetry phoning home, no API keys required.
Key Constraints
- all-MiniLM-L6-v2 max input: 256 tokens. Chunks longer than this must be split for embedding.
- sqlite-vec max dimensions: 8192. We use 384 — well within limits.
- Node 22 LTS only. No
node:sqlite(requires 23.5+). Usebetter-sqlite3. - WASM grammars only. No native Tree-sitter bindings — portable across macOS/Linux/Windows.
- MCP SDK v1.29.0 only. v2 is alpha. Migration is post-MVP.
Contributing
Contributions are welcome! See CONTRIBUTING.md for development setup, code conventions, and the pull request process.
Before contributing, please read our Code of Conduct and Security Policy.
License
MIT © 2026 Raghav Wahi
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。