Skip to main content
Glama
Sign In
mcp-everything-search

mcp-everything-search

by mamertofabian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-everything-search

No user-submitted related servers found.

    Related Servers

    • everything-mcp

      uwx
      A
      license
      A
      quality
      D
      maintenance
      MCP server that integrates Everything file search engine on Windows, enabling fast file and folder searches using Everything syntax, plus version and status checks.
      4
      6 npm
      MIT

    • everything-mcp

      ixijxjgxidj-cmd
      A
      license
      A
      quality
      D
      maintenance
      Ultra-lightweight MCP server that exposes Voidtools Everything's blazing-fast file search to AI agents on Windows. Provides tools for searching, counting, and health checking via Everything's NTFS index.
      3
      517 npm
      MIT

    • everything-mcp

      dengbojing
      F
      license
      A
      quality
      A
      maintenance
      Enables fast Windows file and directory lookups through the local Everything index, supporting exact, keyword, wildcard, regex, fuzzy, pinyin, and typo-tolerant searches with filters, pagination, directory browsing, counting, and status checks.
      12
      -

    • @shxiaj/everything-mcp

      shxiaj
      A
      license
      A
      quality
      D
      maintenance
      Enables lightning-fast file searching on Windows using Everything SDK, with tools for search, version check, status, and file info retrieval.
      4
      9 npm
      MIT

    • everything-mcp-server

      peterparker57
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables instant file searches on Windows using Everything's native SDK, supporting advanced filters, duplicate detection, and content search through MCP tools.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusing it with another. Its purpose (universal file search on Linux via locate) is unambiguous.

    Naming Consistency5/5

    A single tool named 'search' is a clean, conventional name with no competing conventions to clash with. Nothing inconsistent exists in the set.

    Tool Count3/5

    One tool is borderline thin for a server, though a single 'search' entry point is a defensible design. Supporting operations around the search lifecycle (e.g. index refresh) would justify a slightly larger surface.

    Completeness3/5

    Search itself is well-documented with wildcard and regex syntax, but the surface is a thin wrapper over locate with no index-update/reindex operation, which is a real gap since locate results depend on a current database. No output-filtering or result-paging operations are exposed either.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources