Everything MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| everything_searchB | Search files and folders using voidtools Everything ultra-fast search engine. Supports full Everything syntax (e.g. wildcards, ext:ts;js, size:>10mb, dm:today, regex, etc.). |
| everything_find_filesA | Find files by filename, extension, directory location, date range, and size range without manually constructing complex Everything query syntax. |
| everything_find_foldersB | Find folders and directories across the system by name keyword and optional parent directory. |
| everything_get_file_infoB | Retrieve complete indexing metadata and filesystem stats for a specific file or folder path. |
| everything_preview_fileA | Preview text content of a file located via Everything search (includes line numbering and binary detection). |
| everything_statusB | Check Everything search engine connection status, total indexed items in database, and HTTP server endpoint info. |
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 6 tools
Most tools are clearly distinct: status, metadata, preview, and folder search have unique purposes. The main ambiguity is between everything_search and everything_find_files, since both locate files, but descriptions clarify that one is raw-syntax search and the other is structured filtering.
All tools follow a consistent everything_verb_noun pattern in snake_case. The verbs are clear and intuitive, and the shared prefix reinforces the cohesive toolkit.
Six tools is well-scoped for a file-search server. Each tool covers a distinct aspect of the workflow without unnecessary bloat or redundancy.
The toolkit covers the full search lifecycle: querying raw syntax, structured file and folder discovery, metadata retrieval, content preview, and server status. No obvious dead ends or missing core operations for the stated purpose.