Pathgrove
Pathgrove provides local, index-backed file search and inspection through MCP without a hosted search service or API key.
Search filenames and metadata with structured queries, including extension, path, size, date, regex, case/whole-word matching, exclusions, sorting, and pagination.
Search literal text inside files on demand, even before filename indexing finishes.
Search files by type category such as audio, video, image, document, code, archive, executable, font, 3D, and data.
Find recently modified files by time period with optional extension and query filters.
Inspect file or folder metadata and preview text file contents.
Count matching files, calculate total sizes, and break down results by extension.
Check index status, configured roots, and scan errors.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pathgrove find PDF invoices in my Documents from the last 7 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pathgrove
Give your AI assistant a fast way to find your local files.
Pathgrove lets an MCP-compatible assistant find files without knowing their location first. It keeps a reusable filename index, so repeated searches do not have to walk every folder again. Search text inside files, inspect matches and get the paths you need through the same connection.
Ask your assistant:
Find invoice PDFs modified in the last seven days.
Find Python files containing
API_BASE_URL.Show me a preview of
annual-report.txt.
Runs locally on Windows, Linux and macOS. You choose the search folders. Pathgrove needs no hosted search service or API key; your MCP client controls what is sent to its model.
The payoff
On a physical Mac mini M1 with about four million indexed entries, repeated filename searches returned these results:
Search | Fresh filesystem scan | Pathgrove MCP | Speed-up |
| 77.06 seconds | 64 milliseconds | 1,196× |
Broad substring | 77.65 seconds | 2.39 seconds | 32× |
Five trials per query, with identical ordered first-50 result pages checked each time. The comparison is against a fresh Python os.scandir traversal, using a warmed filename index. Indexing and startup are excluded; it is not a comparison against Everything or Spotlight. These measurements describe the recorded baseline, before the later indexing optimizations. Method and raw data →
The first index costs time: that Mac traversal took 17.2 minutes, and inaccessible paths still limited coverage. Start with your project or document folders. Optimized Windows full-drive completion is estimated at about 75 minutes, not measured to completion. Windows measurements and estimate →
Related MCP server: carrel
Get started
Requires Python 3.10+ and uv. See the SQLite requirements.
uv tool install pathgrove-mcpThis puts the pathgrove command on your PATH; pipx install pathgrove-mcp works too. Add this to an MCP client that uses mcpServers configuration:
{
"mcpServers": {
"pathgrove": {
"command": "pathgrove",
"env": {
"PATHGROVE_ROOTS": "[\"<ABSOLUTE_SEARCH_ROOT>\"]"
}
}
}
}Replace <ABSOLUTE_SEARCH_ROOT> with an existing folder you want to search. Forward slashes work on Windows too, avoiding nested backslash escaping. You can put multiple roots in the JSON-encoded array. If the client cannot find pathgrove, use its absolute path (uv tool dir --bin shows the folder), or use "command": "uvx" with "args": ["--from", "pathgrove-mcp", "pathgrove"] without installing.
To run from a checkout instead, clone the repository, run uv sync --frozen and use "command": "uv" with "args": ["run", "--directory", "<ABSOLUTE_CHECKOUT_PATH>", "--frozen", "pathgrove"].
Restart your MCP client and ask it to find a file. Initial indexing runs in the background; committed batches become searchable before it finishes. Keep the server running for filesystem updates. On Windows (NTFS), later restarts read the drive's change journal and revisit only changed folders instead of walking everything again. No administrator rights or other search app are needed.
What it can do
Task | Tool |
Find files by name, path, extension, size or date |
|
Search literal text, even before the index finishes |
|
Find file categories or recent changes |
|
Preview a file or inspect its metadata |
|
Count indexed matches or check index health |
|
Search from a terminal or script |
|
Examples of filename queries:
invoice ext:pdf dm:last7days
"annual report" !draft
ext:py content:"API_BASE_URL"Know the limits
Search stays inside your configured roots and respects normal filesystem permissions. Links are not followed.
The index stores names, paths and metadata. Text is read from disk per query; PDF/Word extraction and OCR are not included.
Building indexes, inaccessible files and query budgets can produce partial results. A partial miss does not prove absence. The tools report these limits explicitly.
Read more
CI tests Python 3.10 and 3.14 across Linux, Windows and ARM/Intel macOS. Linux tests, lint and package builds use Ubicloud (ubicloud-standard-2); Windows and macOS use native GitHub-hosted runners. Forks need the Ubicloud app connected to run those Linux jobs.
Available Tools
7 toolspathgrove_count_statsARead-onlyIdempotent
Get count and size statistics for files matching a query.
Fast way to understand the scope of a query without listing every file. Optionally breaks down by extension for a high-level overview.
Inputs: params (required). Returns: result
pathgrove_file_detailsARead-onlyIdempotent
Get detailed metadata and optional content preview for specific files.
Returns: full path, size, dates, type, permissions, hidden status. For directories: item count, subdirectories, file listing. For text files with preview_lines > 0: first N lines of content.
Inputs: params (required). Returns: result
pathgrove_find_recentARead-onlyIdempotent
Find files modified within a recent time period.
Ideal for discovering what changed in a project, tracking recent downloads, finding today's log files, etc. Sorted newest-first.
Inputs: params (required). Returns: result
pathgrove_index_statusARead-onlyIdempotent
Report independent index readiness, configured roots and last scan errors.
A building index may serve cached rows while reconciliation is in progress. This tool does not trigger a full rescan or require any external application.
Inputs: no named parameters. Returns: result
pathgrove_searchBRead-onlyIdempotent
Search configured roots using our own SQLite filename/metadata index.
No external application, background search service or GUI is required. The first build may take time; pathgrove_index_status reports progress.
Inputs: params (required). Returns: result
pathgrove_search_by_typeBRead-onlyIdempotent
Search for files by type category.
Categories: audio, video, image, document, code, archive, executable, font, 3d, data. Each maps to a curated list of file extensions.
Inputs: params (required). Returns: result
pathgrove_search_contentARead-onlyIdempotent
Search text directly on disk without waiting for the filename index.
Recurses within configured roots; returns matches in traversal order. UTF-8 and BOM-marked UTF-16/32 are supported. Time/read/file limits and skipped files are explicitly reported. No date ordering or global pagination.
Inputs: params (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
The tools mostly have distinct purposes: indexed filename search, direct content search, type-based search, recent-file search, details, stats, and index status. Some boundary overlap exists between general search, type search, and recent search, but the descriptions make the intended distinctions reasonably clear.
All tools use a consistent pathgrove_ prefix and snake_case, which makes the set predictable. The suffixes mix action-oriented verbs (search, find_recent) with noun/status forms (index_status, file_details, count_stats), but this is readable and mostly coherent.
Seven tools is well-scoped for a file search and indexing server. Each tool covers a distinct workflow: indexed search, content search, type filtering, recency, details, stats, and index readiness.
The surface covers core file discovery, content search, metadata inspection, statistics, and index status. Minor gaps remain around explicitly configuring roots, triggering a rebuild/rescan, or retrieving full file contents, but the main search workflows are represented.
Maintenance
Related MCP Connectors
Securely search and manage workspace context files for AI agents and teams.
Agentic search over your Dewey document collections from any MCP-compatible client.
Search and inspect source-pinned agent skills, plugins and tools through a free public MCP.
Web search API and MCP server for developers building AI agents.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to intelligently search and explore local file systems using native Unix commands (ripgrep, find, ls) with token-optimized output, automatic pagination, and multi-layer security validation.164 npm2-
- AlicenseAqualityBmaintenanceEnables local file search, packing into LLM-ready context, and inspection via an MCP server on stdio.1450 PyPI2MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLM agents and MCP clients to read, list, write, search, watch, and batch-process files within configured allowed directories, while exposing discoverable file resources and structured error codes.-
- FlicenseBqualityCmaintenanceEnables any MCP-compatible client to perform filesystem operations — reading, listing, writing, searching, watching directories, and batch processing files — over JSON-RPC 2.0 stdio transport. Includes resource discovery, metrics tracking, and security controls such as allowed roots, size limits, and format allowlists, with a LangGraph agent that accesses files exclusively through MCP.6-