Skip to main content
Glama
FreeXMelody

Everything MCP Enhanced

by FreeXMelody
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EVERYTHING_BASE_URLNoThe base URL of the Everything HTTP server (e.g., http://127.0.0.1:8011). Optional; if not set, the server automatically detects the port by probing common ports (8011, 80, 8080, 54321) and inspecting Everything.ini.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
everything_searchA

Search Windows files and folders instantly via voidtools Everything index with millisecond latency. Features:

  • Ultra-fast millisecond-level response (5-30ms) across 10M+ indexed files, eliminating slow recursive terminal scans (dir /s, Get-ChildItem).

  • Zero disk I/O thrashing (queries in-memory index directly).

  • Supports dedicated 'path' parameter to scope into specific drive or folder (e.g. 'D:\Projects').

  • Built-in 'exclude_noise' filter (default: true) to eliminate node_modules/.git/.venv clutter.

  • Token-saving 'compact' format (default: true, 1 line per file path) saving 75%+ tokens.

  • Max count up to 5000 results without artificial hard 100-item cutoff.

everything_healthA

Check connectivity to local voidtools Everything HTTP server and report index statistics.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: everything_search performs file/folder queries against the Everything index, while everything_health reports connectivity and index statistics. There is no plausible scenario where an agent would confuse them.

Naming Consistency5/5

Both tools follow the same snake_case convention with a consistent 'everything_' prefix (everything_search, everything_health). The verb/noun structure is predictable and readable.

Tool Count3/5

With only 2 tools, the surface is thin for a server that advertises enhanced Everything functionality. The search and health tools are well-scoped, but the small count limits the value proposition compared to typical 3-15 tool servers.

Completeness4/5

Search plus health covers the core workflow of querying the Everything index and verifying the backend is alive. Minor gaps exist—such as no dedicated tool for retrieving file metadata or enumerating indexed drives—but agents can work around these via search parameters.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources