Everything File Search vs Markitdown

A side-by-side look at the Everything File Search and Markitdown MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Everything File Search logoEverything File SearchFile Systems · Local subprocess (stdio)Lightning-fast Windows file search for AI agents via voidtools Everything's real-time NTFS index64GoodAuth: no auth requiredMarkitdown logoMarkitdownFile Systems · Local subprocess (stdio)MCP tool access to MarkItDown -- a library that converts many file formats (local or remote) to Markdown for LLM consumption.59GoodAuth: no auth required

Verdict: choose Everything File Search for file systems work as a local process; choose Markitdown 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?

Everything File Search logoChoose 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.
Explore Everything File Search

Markitdown logoChoose Markitdown 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.
Explore Markitdown

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEverything File Search logoEverything File SearchMarkitdown logoMarkitdown
CategoryFile SystemsFile Systems
Quality signal64/100 · Good59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars29191,657
Directory activity 4 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools5Not listed

Tools & capabilities

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.

Markitdown tools

No tool names declared yet. Check the project README from the listing page.

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.

Everything File Search

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "everything-file-search": {
      "command": "uvx",
      "args": [
        "everything-mcp"
      ]
    }
  }
}

Markitdown

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "microsoft-markitdown": {
      "command": "uvx",
      "args": [
        "markitdown-mcp"
      ]
    }
  }
}

Frequently asked questions

Everything File Search is categorized under File Systems and uses a local stdio subprocess. Markitdown belongs to File Systems and uses a local stdio subprocess. Pick Everything File Search for file systems work and Markitdown 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.

Everything File Search is listed as free. Auth: no auth required. Markitdown 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 everything-file-search and microsoft-markitdown as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Everything File Search has a quality signal of 64/100 (Good) with 4 views, 0 installs and 29 GitHub stars. Markitdown has 59/100 (Good) with 6 views, 0 installs and 191,657 GitHub stars.