Local file search for AI agents — semantic + keyword indexing over your codebase.
MCPpedia last refreshed this data
io.github.roshunsunder/filesift is an MCP server that local file search for AI agents — semantic + keyword indexing over your codebase. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 77/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"filesift": {
"command": "filesift-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Local file search for AI agents — semantic + keyword indexing over your codebase.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
uvx 'filesift' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked filesift against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in search / developer-tools
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Manage Supabase projects — databases, auth, storage, and edge functions
MCP server for using the GitLab API
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
MCP Security Weekly
Get CVE alerts and security updates for io.github.roshunsunder/filesift and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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:
pip install filesift
There are three ways to use FileSift, depending on your workflow:
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
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 directoryFileSift 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.
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 index first 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.
FileSift uses a TOML configuration file, manage