mcp-everything-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERYTHING_SDK_PATH | No | Windows only (required there): full path to Everything64.dll from the Everything SDK. Not used on Linux/macOS. | |
| EVERYTHING_SEARCH_TOOL_NAME | No | Optional tool name (default: search). Letters, digits, _ and -, 1-64 characters. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Universal file search tool for Linux Current Implementation: Using locate with Unix-style search capabilities Search Syntax Guide: Linux Locate Search Syntax: Basic Usage:
Pattern Wildcards:
Examples:
|
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 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose (universal file search on Linux via locate) is unambiguous.
A single tool named 'search' is a clean, conventional name with no competing conventions to clash with. Nothing inconsistent exists in the set.
One tool is borderline thin for a server, though a single 'search' entry point is a defensible design. Supporting operations around the search lifecycle (e.g. index refresh) would justify a slightly larger surface.
Search itself is well-documented with wildcard and regex syntax, but the surface is a thin wrapper over locate with no index-update/reindex operation, which is a real gap since locate results depend on a current database. No output-filtering or result-paging operations are exposed either.