Vibe Hnindex
Index your repo into a local knowledge base and let the agent search it with keyword, semantic, or hybrid retrieval instead of grepping blind.
Overview
Vibe HNIndex is a MCP server for the Build phase that indexes source code locally and serves keyword, semantic, and hybrid search to coding agents over stdio.
What is this MCP server?
- Indexes source code into a local knowledge base backed by SQLite (STORAGE_PATH)
- Three search modes: keyword, semantic, and hybrid
- stdio npm package vibe-hnindex v0.1.2 with Ollama embeddings (OLLAMA_URL, OLLAMA_MODEL default bge-m3:567m)
- Qdrant vector store via QDRANT_URL for semantic chunks
- Self-hosted stack—no mandatory cloud index vendor in server.json
- Package version 0.1.2
- Search modes: keyword, semantic, hybrid (3)
- Default OLLAMA_MODEL: bge-m3:567m
Community signal: 4 GitHub stars.
What problem does it solve?
Agents lose context in big codebases because full-repo context windows are expensive and brittle.
Who is it for?
Solo devs with MCP clients who already run or can run Ollama and Qdrant and want private codebase RAG.
Skip if: Teams that want zero local infra or instant cloud-only codebase search with no embedding setup.
What do I get? / Deliverables
After indexing, your agent queries a local KB with keyword, semantic, or hybrid search grounded in your actual files.
- Indexed local knowledge base of project source files
- MCP tools for keyword, semantic, and hybrid code search
- Repeatable agent workflows grounded in retrieved snippets
Recommended MCP Servers
Journey fit
Primary shelf is build agent-tooling because indexing and search are how you equip the agent while you ship code. Local Qdrant plus SQLite storage is an integration layer between your codebase and the model—not a deploy or SEO task.
How it compares
Local code-index MCP with triple search modes, not a hosted documentation SaaS or single-purpose grep skill.
Common Questions / FAQ
Who is vibe-hnindex for?
Builders and agent users who want private, local retrieval over their own repositories using Ollama embeddings and Qdrant.
When should I use vibe-hnindex?
Use it when you start sustained work on a large repo, during reviews, or when iterating so the agent can search indexed sources instead of guessing paths.
How do I add vibe-hnindex to my agent?
Install the npm package vibe-hnindex (v0.1.2), set OLLAMA_URL, OLLAMA_MODEL, QDRANT_URL, and STORAGE_PATH, then register the stdio MCP server in your agent config.