Pathgrove
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATHGROVE_DB | No | Persistent SQLite metadata cache path. | Application cache directory / pathgrove/index.sqlite3 |
| PATHGROVE_ROOTS | No | JSON array of directory or drive roots to index. Without PATHGROVE_ROOTS, only the current user's home directory is indexed. | Current user's home directory |
| PATHGROVE_TIMEOUT | No | Query budget in seconds. | 10 |
| PATHGROVE_MAX_RESULTS | No | Backend result cap. MCP search requests also have a 500-result cap. | 1000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pathgrove_searchB | 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. |
| pathgrove_search_contentA | 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. |
| pathgrove_search_by_typeB | 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. |
| pathgrove_find_recentA | 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. |
| pathgrove_file_detailsA | 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. |
| pathgrove_count_statsA | 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. |
| pathgrove_index_statusA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_status | Read own-index build state, roots, entry count and watcher diagnostics. |
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.