yoanbernabeu/grepai
Semantic Search & Call Graphs for AI Agents (100% Local)
What it solves
Traditional search tools like grep rely on exact text matching, which makes it difficult to find code based on its purpose or logic. grepai solves this by enabling semantic search, allowing developers to find code based on what it does rather than how it is named, while also reducing the number of tokens consumed by AI agents by providing only relevant context.
How it works
grepai uses vector embeddings to index your codebase locally. It runs as a background daemon that watches your files to keep the index up-to-date. You can query this index using natural language, trace function call graphs, or use it as an MCP server to provide context directly to AI coding assistants like Claude Code, Cursor, or Windsurf.
Who it’s for
It is designed for developers who want to navigate large codebases more efficiently, reduce AI token usage, and maintain strict data privacy by keeping all code analysis local to their machine.
Highlights
- Search by intent (e.g., finding "authentication logic" instead of specific function names).
- 100% local processing ensures your code never leaves your machine.
- Automatically keeps the search index updated via a file-watching daemon.
- Integrates directly with AI agents as an MCP server.
- Supports call graph tracing to identify function dependencies.
- Compatible with multiple embedding providers including Ollama, LM Studio, and OpenAI.
Related
- Project
- Project
- Project
- Project
- Project