Local Workspace MCP vs Everything File Search
A side-by-side look at the Local Workspace MCP and Everything File Search MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Local Workspace MCP for file systems work; choose Everything File Search for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Local Workspace MCP when
- You need dedicated capabilities in the File Systems domain.
- Its auth model fits you: No auth required.
Choose Everything File Search when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
everything_search, everything_search_by_type, everything_find_recent.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 32/100 · Emerging | 65/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 26 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Local Workspace MCP | View Everything File Search |
Tools & capabilities
Local Workspace MCP tools
No tool names declared yet. Check the project README from the listing page.
Everything File Search tools 5
everything_searchSearch for files and folders instantly using voidtools Everything. Leverages Everything's real-time NTFS index for sub-millisecond search across all local and mapped drives. Supports wildcards, regex, size/date filters, extension filters, and path restrictions.everything_search_by_typeSearch for files by type category. Categories: audio, video, image, document, code, archive, executable, font, 3d, data. Each maps to a curated list of file extensions.everything_find_recentFind files modified within a recent time period. Ideal for discovering what changed in a project, tracking recent downloads, finding today's log files, etc. Sorted newest-first.everything_file_detailsGet detailed metadata and optional content preview for specific files. Returns: full path, size, dates, type, permissions, hidden status. For directories: item count, subdirectories, file listing. For text files with preview_lines > 0: first N lines of content.everything_count_statsGet count and size statistics for files matching a query. Fast way to understand the scope of a query without listing every file. Optionally breaks down by extension for a high-level overview.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Local Workspace MCP
No confirmed install command for Local Workspace MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Everything File Search
{
"mcpServers": {
"everything-file-search": {
"command": "uvx",
"args": [
"everything-mcp"
]
}
}
}
Frequently asked questions
Local Workspace MCP is categorized under File Systems and uses an install path we have not confirmed yet. Everything File Search belongs to File Systems and uses a local stdio subprocess. Pick Local Workspace MCP for file systems work and Everything File Search for file systems.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Local Workspace MCP has no confirmed install command yet — follow its own setup instructions.
Local Workspace MCP is listed as free. Auth: no auth required. Everything File Search is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add local-workspace-mcp and everything-file-search as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Local Workspace MCP has a quality signal of 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Everything File Search has 65/100 (Great) with 3 views, 0 installs and 26 GitHub stars.