everything-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| everything_statusA | Report whether Everything is reachable and its index is ready. Call this to self-diagnose before searching: returns |
| search_filesA | Instantly search file and folder NAMES across the entire disk using the Everything index (use this instead of recursive directory listings when the target is outside the current project).
Searches names only, NOT file contents. |
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 serve clearly distinct purposes: one checks the status of the Everything index, the other performs searches. There is no overlap or ambiguity between them.
The tool names follow different patterns: 'search_files' is verb_noun, while 'everything_status' is a noun phrase. Both are readable and use snake_case, but the inconsistency in pattern is noticeable.
With only two tools, the server is minimal. The search tool is the core functionality and the status tool is a useful helper, but the set feels slightly thin for a full-featured server.
The server fully covers its stated purpose of searching file names via the Everything index. The search tool offers extensive query syntax and pagination, while the status tool provides essential readiness information. No obvious gaps for the intended use case.