The Everything Search MCP Server integrates with the Everything Search Engine to provide powerful file search capabilities:
Perform full text searches across files and directories
Use advanced search options including case sensitivity, whole word matching, regular expressions, and path-specific searches
Configure search parameters such as scope, maximum results, and custom sorting
Sort results by name, path, size, or date modified in ascending or descending order
Format results with human-readable file sizes, formatted dates, and full paths
Provides powerful file search capabilities through integration with Everything Search Engine, allowing for full text search across files and directories with advanced filtering options, sorting, and customizable result formats.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Everything Search MCP Server find all PDF files in my Documents folder modified this week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that provides integration with Everything Search Engine, allowing powerful file search capabilities through the Model Context Protocol.
Full text search across files and directories
Advanced search options:
Case sensitive search
Whole word matching
Regular expressions
Path search
Sorting options:
By name
By path
By size
By date modified
Result formatting:
Human-readable file sizes
Formatted dates
Full file paths
Related MCP server: Everything Search MCP Server
Node.js 16 or higher
Everything Search Engine with HTTP Server enabled
Open Everything Search
Go to Tools > Options > HTTP Server
Enable HTTP Server
Set the HTTP Server port to 8011 (this is the default port used by this MCP server)
Click OK to save changes
Note: If you need to use a different port, you'll need to modify the port in src/server.ts where it connects to http://127.0.0.1:8011/
npm install
npm run buildThe server provides a single tool through MCP:
use_mcp_tool:
- server_name: everything-search
- tool_name: search
- arguments:
{
"query": "search string", // Required: Text to search for
"scope": "C:", // Optional: Search scope (default: C:)
"caseSensitive": false, // Optional: Match case
"wholeWord": false, // Optional: Match whole words only
"regex": false, // Optional: Use regular expressions
"path": false, // Optional: Search in paths
"maxResults": 100, // Optional: Max results (1-1000, default: 100)
"sortBy": "name", // Optional: Sort by name/path/size/date_modified
"ascending": true // Optional: Sort direction
}Basic file search:
{
"query": "*.txt",
"maxResults": 5
}Advanced search with filters:
{
"query": "test",
"scope": "C:\\Users",
"caseSensitive": true,
"wholeWord": true,
"maxResults": 10,
"sortBy": "date_modified",
"ascending": false
}Regex search in paths:
{
"query": ".*\\.js$",
"regex": true,
"path": true,
"maxResults": 5
}ISC
Search for files using Everything Search
Inputs: query, scope, caseSensitive, wholeWord, +5 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single 'search' tool has a clear and distinct purpose that cannot be confused with any other tool in this set.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare it against. The name 'search' follows a simple, clear verb pattern appropriate for its function.
A single tool is too few for most server purposes, as it severely limits functionality and flexibility. While it matches the server's name ('Everything Search'), a search-focused server could benefit from additional tools like filtering, sorting, or advanced query options to enhance usability.
The tool surface is severely incomplete for a search domain. With only a basic search tool, there are significant gaps such as no ability to configure search parameters, handle search results (e.g., pagination or sorting), or perform related operations like indexing management or search history.
Securely search and manage workspace context files for AI agents and teams.
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Read and search folders on your own computer with explicit consent. Files are never uploaded.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…