voidtools-everything-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERYTHING_BASE_URL | No | Everything HTTP Server URL | http://127.0.0.1 |
| EVERYTHING_MAX_COUNT | No | Maximum returned result count | 100 |
| EVERYTHING_TIMEOUT_MS | No | HTTP timeout in milliseconds | 5000 |
| EVERYTHING_DEFAULT_COUNT | No | Default returned result count | 20 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| everything_searchA | Search local Everything index. Read-only. Returns bounded file and folder paths. |
| everything_healthA | Check whether the Everything HTTP Server is reachable. |
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 2 tools
The two tools have clearly distinct purposes: one checks server health, the other performs searches. No overlap or ambiguity.
Both tools follow the consistent pattern 'everything_<action>', using snake_case and the same prefix for clear grouping.
Two tools is minimal but appropriate for a simple read-only search interface with a health check. Just above the threshold for being too few.
The set covers the essential operations: verifying connectivity and searching. Missing advanced search features but adequate for basic usage.