io.github.roshunsunder/filesift
Local file search for AI agents — semantic + keyword indexing over your codebase.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
filesiftclaude mcp add filesift -- uvx filesift==0.2.1
{
"mcpServers": {
"filesift": {
"command": "uvx",
"args": [
"filesift==0.2.1"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
FileSift
A local, open-source utility that helps AI coding agents intelligently search and understand codebases.
FileSift lets your AI coding agent search across a codebase based on what code does, rather than what it looks like. Instead of sifting through entire files after a grep, your agent can jump straight to the most relevant code using natural language queries like "authentication middleware" or "database connection pooling". Everything runs locally on your machine — your code never leaves your environment.
Key benefits:
- Smarter search — hybrid keyword + semantic search finds code by intent, not just string matching
- Less context wasted — agents get pointed to the right files immediately, saving token budget on exploration
Installation
pip install filesift
Usage
There are three ways to use FileSift, depending on your workflow:
1. CLI
The most straightforward approach. Good for testing queries, managing indexes, and configuring settings.
# Index a project
filesift index /path/to/your/project
# Search for files by what they do
filesift find "authentication and session handling"
# Search in a specific directory
filesift find "retry logic for API calls" --path /path/to/project
2. MCP Server
Installing FileSift also provides a filesift-mcp command — a lightweight MCP server that exposes indexing and search as tools over STDIO. This works with most popular coding agents including Claude Code, Cursor, Copilot, and more.
Add it to your agent's MCP configuration:
{
"mcpServers": {
"filesift": {
"command": "filesift-mcp"
}
}
}
The MCP server exposes four tools:
filesift_search— search an indexed codebase by natural language queryfilesift_find_related— find files related to a given file via imports and semantic similarityfilesift_index— index a directory to enable searchingfilesift_status— check indexing status of a directory
3. Skills
FileSift ships with a search-codebase skill that can be installed directly into your coding agent's skill directory. This lets the agent interact with the FileSift CLI through bash, without requiring MCP support.
# Install for Claude Code (default)
filesift skill install
# Install for other agents
filesift skill install --agent cursor
filesift skill install --agent copilot
filesift skill install --agent codex
Supported agents: claude, codex, cursor, copilot, gemini, roo, windsurf.
How It Works
FileSift uses a daemonized embedding model to keep searches fast. At its core, it generates embeddings from code descriptions and performs searches against small vector stores called indexes.
- Indexing —
filesift indexfirst builds a fast keyword/structural index (completes in seconds), then triggers background semantic indexing that generates embeddings for each file. - Daemon — A background daemon loads indexes into memory and automatically shuts down after a configurable period of inactivity. After the first cold-start search, subsequent searches are near-instant.
- Search — Queries are matched using both keyword (BM25) and semantic (FAISS) search, then combined via Reciprocal Rank Fusion for the best of both approaches.
Indexes are stored in a .filesift directory within each indexed project.
Configuration
FileSift uses a TOML configuration file, manageable via the CLI:
# View all settings
filesift config list --all
# Set a value
filesift config set search.MAX_RESULTS 20
filesift config set daemon.INACTIVITY_TIMEOUT 600
# Manage ignore patterns
filesift config add-ignore "node_modules" ".venv"
filesift config list-ignore
Configuration sections: search, indexing, daemon, models, paths.
Contributing
Contributions are welcome! To get started:
git clone https://github.com/roshunsunder/filesift.git
cd filesift
pip install -e .
- Fork the repository
- Create a feature branch (
git checkout -b feature/my-feature) - Commit your changes and open a pull request
License
Apache 2.0 — see LICENSE for details.
Frequently asked questions
What is io.github.roshunsunder/filesift?
Local file search for AI agents — semantic + keyword indexing over your codebase.
How do I install io.github.roshunsunder/filesift?
It runs on your machine. In Claude Code: claude mcp add filesift -- uvx filesift==0.2.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.roshunsunder/filesift need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.roshunsunder/filesift open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains io.github.roshunsunder/filesift?
It is published by roshunsunder. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.