Enhanced Everything MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERYTHING_PATH | No | Path to the Everything command-line interface (es.exe) | C:\Program Files\Everything\es.exe |
| TRACE_DIRECTORY | No | Directory path for storing trace logs and debugging information | D:\outputs\traces |
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_searchC | Search for files and folders using Everything search engine |
| everything_search_advancedC | Advanced search with filtering and sorting options |
| everything_check_serviceA | Check if Everything service is running and accessible |
| everything_search_docsA | Search for documentation, specifications, and requirement files optimized for SpecStory workflows |
| everything_tui_launchA | Launch the Terminal User Interface for interactive project management and search |
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 5 tools
The three search tools (everything_search, everything_search_advanced, everything_search_docs) share overlapping purposes, and an agent might struggle to choose the right one. The advanced and docs variants have clear modifiers, but the boundary between basic and advanced is not stark. The service check and TUI launch are clearly distinct.
All tools share the everything_ prefix and use snake_case, which creates a strong family identity. The verb forms are consistent (search, check, launch), though search_advanced and search_docs use different syntactic structures (adjective vs noun). Overall, the naming is predictable and readable.
With 5 tools, the server is well-scoped for its purpose. It provides a reasonable set of search capabilities (basic, advanced, docs-specific), a service health check, and a TUI launcher without bloating the surface. This count is appropriate for an Everything integration.
The tool set covers the core search workflows and includes a service check and TUI launch. Missing operations like starting/stopping the service or updating the index are minor and can be worked around. Overall, the major use cases are addressed with no critical dead ends.