everything-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERYTHING_SDK_DIR | No | Path to the Everything SDK directory | ./Everything-SDK-3.0.0.9/dll |
| EVERYTHING_DLL_PATH | No | Full path to the Everything DLL | $SDK_DIR/Everything3_x64.dll |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| everything_searchA | Search for files and folders on Windows using Everything. Everything search syntax supports:
Examples: "ext:jpg size:>1mb", "*.ts", "folder:node_modules", "content:TODO" |
| everything_versionA | Get the version information of the running Everything search engine. |
| everything_statusA | Check if the Everything search engine is running and its database is loaded. |
| everything_file_infoA | Get file attributes (Windows attributes, run count) for a specific file path using Everything. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: searching, retrieving file attributes, checking version, and checking service status. There is no overlap between them, so an agent can easily select the right one.
All tools share the 'everything_' prefix and use snake_case, but the second part mixes nouns (file_info, version, status) and a verb (search). This is a minor deviation from a strict verb_noun pattern but remains predictable and readable.
With 4 tools, the server is well-scoped for interacting with the Everything search engine. Each tool covers a necessary aspect without redundancy or bloat.
The tool surface covers the core functionality: searching, getting file metadata, and checking the engine's operational state. Minor gaps like advanced query analysis or database statistics exist but are not essential for basic usage.