Enhanced Everything MCP Server
Related Servers
Alternatives to Enhanced Everything MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search local files on Windows using the Everything search engine, supporting basic and complex file searches with filters like date, size, media type, and document type.4MIT
- FlicenseAqualityAmaintenanceEnables AI assistants to search local files and folders via the Everything search engine, with support for advanced queries, file metadata, text previews, and service status.6-
- AlicenseNot gradedqualityAmaintenanceEnables instant file and folder searching on Windows using Everything's blazing-fast search engine, supporting powerful search syntax including wildcards, regex, size filters, date filters, and comprehensive file information retrieval.545 npm12MIT
- FlicenseAqualityDmaintenanceIntegrates Everything Search with Claude Code for lightning-fast file searching across entire drives, up to 400x faster than traditional methods.5-
- AlicenseNot gradedqualityDmaintenanceEnables instant file searches on Windows using Everything's native SDK, supporting advanced filters, duplicate detection, and content search through MCP tools.5MIT
- AlicenseAqualityCmaintenanceEnables lightning-fast file searching on Windows using Everything SDK, with tools for search, version check, status, and file info retrieval.413 npmMIT
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.