The Everything Search MCP server exposes voidtools Everything, the Windows file search utility, to an agent. Everything maintains an index of every filename on your drives and returns results as you type, and having that available as a tool solves the surprisingly common problem of an agent knowing a file exists but not where.
What it actually does
The server queries the running Everything index and returns matching paths. Because the index is already built and held in memory, results come back effectively instantly regardless of how many files you have. The agent can search by name, extension, path fragment, and Everything’s own query syntax.
Practical patterns:
- ‘Find every .env file on this machine.’
- ‘Where is the config for that project? I think it has “invoice” in the name.’
- ‘List every PDF modified in the last week across all drives.‘
Why use it
It pairs naturally with the Filesystem server, which reads files but needs to be told where they are. Everything supplies the where. The combination means you can ask an agent to work with a file you cannot locate yourself, which is a routine situation on a machine that has been in use for years.
Gotchas
Windows only, and Everything itself must be installed and running with its index built. The name clashes confusingly with Anthropic’s Everything reference server, which does something completely different, so check which one you are configuring. It searches names and paths rather than contents, so “find the document that mentions X” is not what it does. And it will happily surface files across your entire machine, which is worth remembering before pointing an agent at it on a shared computer.
