Skip to main content
Glama
QuickerHub

@quickerhub/everything-mcp

by QuickerHub
README.md
# @quickerhub/everything-mcp

Fast cross-project file search for AI agents via [voidtools Everything](https://www.voidtools.com/) on Windows.

Uses the **Everything SDK DLL** (same approach as QuickerPc), not `es.exe`.

Published by [QuickerHub](https://github.com/QuickerHub).

## Architecture

```
Cursor / Claude / VS Code
  → everything-mcp.exe (MCP stdio)
  → Everything64.dll (bundled SDK IPC client)
  → Everything.exe (user-installed tray client + index engine)
```

The bundled DLL is only an IPC client. **Everything.exe must be installed and running** to maintain the file index.

## Prerequisites

1. **Windows x64**
2. [.NET 8 Runtime](https://dotnet.microsoft.com/download/dotnet/8.0)
3. [Everything](https://www.voidtools.com/) 1.4.x installed (stable). Tray client should be running.
4. Node.js 18+ (only for `npx` launcher)

No `es.exe` / ES CLI required.

## MCP config

### Direct exe (recommended for local dev)

```json
{
  "mcpServers": {
    "everything-search": {
      "command": "D:\\source\\repos\\quicker\\everything-mcp\\publish\\cli\\everything-mcp.exe",
      "args": []
    }
  }
}
```

Build first:

```powershell
cd D:\source\repos\quicker\everything-mcp
.\build.ps1 -Publish
```

### npm launcher

```json
{
  "mcpServers": {
    "everything-search": {
      "command": "npx",
      "args": ["-y", "@quickerhub/everything-mcp"]
    }
  }
}
```

Override exe path:

```json
{
  "env": {
    "EVERYTHING_MCP_EXE": "D:\\path\\to\\everything-mcp.exe"
  }
}
```

## Tools

| Tool | Description |
|------|-------------|
| `search` | Search files/folders via Everything index (returns JSON) |
| `status` | Check bundled SDK DLL and Everything client state |

### `search` parameters

| Parameter | Description |
|-----------|-------------|
| `query` | Everything query (`ext:cs`, wildcards, etc.) |
| `max_results` | Default 100, max 1000 |
| `scope_path` | Limit to folder subtree |
| `match_path` | Match full path |
| `match_case` | Case-sensitive |
| `match_whole_word` | Whole words only |
| `regex` | Regex mode |
| `sort_by` | `name_asc`, `date_modified_desc`, ... |
| `auto_start` | Try starting Everything tray client (default true) |

### Example

```json
{
  "query": "quicker-rpc",
  "scope_path": "D:\\source\\repos\\quicker",
  "max_results": 20
}
```

## Development

```powershell
.\build.ps1          # build only
.\build.ps1 -Publish # publish to publish/cli
.\publish\cli\everything-mcp.exe --smoke-test
```

## Release

**Latest:** https://github.com/QuickerHub/everything-mcp/releases/latest

```powershell
.\publish\Publish-GitHubRelease.ps1 -Version 0.2.0
gh release create v0.2.0 --title "v0.2.0" artifacts/*
```

### npm (`@quickerhub/everything-mcp`)

Requires `NPM_TOKEN` repo secret (npm automation token with publish access to `@quickerhub`).

```powershell
gh secret set NPM_TOKEN --repo QuickerHub/everything-mcp
gh workflow run publish.yml --repo QuickerHub/everything-mcp -f version=0.2.0
```

Creating a GitHub Release also triggers the npm publish workflow automatically.

## Comparison with QuickerPc

| | QuickerPc | everything-mcp |
|--|-----------|----------------|
| SDK DLL | `Everything64.dll` bundled | same |
| Everything.exe | user-installed, required | same |
| IPC | P/Invoke | P/Invoke |
| es.exe | not used | not used |

## Related

- [QuickerHub/quicker-rpc](https://github.com/QuickerHub/quicker-rpc)
- [voidtools SDK](https://www.voidtools.com/support/everything/sdk/)

## License

MIT. Everything SDK DLL is from voidtools (public SDK); not affiliated with voidtools.

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one for searching files, one for checking service status. No overlap or ambiguity.

Naming Consistency5/5

Both tools use a consistent single-word verb pattern ('search', 'status'), clear and predictable.

Tool Count3/5

With only two tools, the server feels thin for a search utility, but it might be sufficient for a minimal integration. Borderline between too few and acceptable.

Completeness2/5

Missing many expected search capabilities like path exclusions, indexing control, or advanced filters. The surface is incomplete for a robust search tool.

Maintenance

ActivityInactive
ResponsivenessNo issues