mcp-everything-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ES_EXE_PATH | Yes | Path to es.exe (Everything CLI), e.g., D:\WORKSPACE\tools\common\es.exe |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_filesA | Search for files and folders by name pattern using Everything Search (extremely fast). Supports wildcards (* and ?) and regex patterns. Use this instead of find, ls, or Glob for much faster results. |
| search_recentA | Find files modified within the last N hours. Extremely fast way to find recently changed files. Much faster than using find with -mtime. |
| search_largeA | Find the largest files in a directory. Useful for finding files that take up the most space. Results are sorted by size (largest first). |
| search_by_extensionB | Search for files by type category (code, docs, media, config, data) or custom extensions. Fast way to find all files of a certain type. |
| search_in_pathA | Search for files within a specific directory. Use this to limit search scope to a particular folder. Much faster than recursive directory scans. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Everything Search Documentation | Complete documentation for es.exe command-line interface |
| Quick Reference | Quick reference for common search patterns and examples |
TDQS
Scored across 5 tools
Each tool targets a distinct search filter (name, recency, size, extension, path), but there is some overlap since search_files can mimic the others with wildcards and path prefixes. The descriptions clearly explain the intended use cases, so confusion is limited.
All tool names follow the consistent pattern 'search_<criterion>', using snake_case throughout. The naming is predictable and easy to understand.
Five tools is well-scoped for a file-search server, covering the most common search criteria without unnecessary bloat. Each tool has a clear purpose and the set feels complete for the domain.
The toolset covers major file search dimensions: name, recency, size, extension, and path. Minor gaps exist, such as searching by exact size range or creation date, but these are edge cases and the core workflow is well supported.