evryth-mcp
English | 简体中文
通过 MCP 调用 Windows 本机 Everything 索引,查找文件和目录。提供 12 个搜索及辅助工具,支持路径、扩展名、大小和修改日期筛选,返回完整路径及文件元数据。
安装准备
当前版本仅支持在 Windows 上运行,依赖本机 Everything 和 ES;macOS、Linux 及其他 Unix 类系统暂不支持原生运行。
需安装 Everything、ES 和 uv(提供 uvx),Python 版本要求为 3.11+。通过 PyPI 安装,无需 Git 或克隆仓库。
- 从 voidtools 下载页 安装 Everything,并保持运行。
- 在同一页面下载 Everything Command-line Interface(ES),解压到固定目录。
- 将 es.exe 所在目录加入 Windows 用户或系统 PATH,然后重启终端和 MCP 客户端。
Everything 与 ES 是不同组件。如果已安装全局 ES,且客户端能从 PATH 找到它,无需设置 EVERYTHING_ES_PATH。
验证安装:
es -version
MCP 配置
使用 uvx evryth-mcp 从 PyPI 自动安装并启动,无需提前执行 pip install。
适用于使用 mcpServers JSON 格式的客户端:
{
"mcpServers": {
"everything-es": {
"command": "uvx",
"args": ["evryth-mcp"]
}
}
}
连接后调用 everything_status,确认返回 connected: true。
如果 ES 已在客户端 PATH 中且使用默认 Everything 实例,上面的配置即可,无需添加环境变量。
需要指定 ES 路径或命名实例时,在 everything-es 配置中添加 env:
{
"mcpServers": {
"everything-es": {
"command": "uvx",
"args": ["evryth-mcp"],
"env": {
"EVERYTHING_ES_PATH": "D:\\Tools\\Everything\\es.exe",
"EVERYTHING_INSTANCE": "Work"
}
}
}
}
EVERYTHING_ES_PATH:替换为实际es.exe的绝对路径,不是Everything.exe或目录;客户端能从 PATH 找到 ES 时可删除此项。EVERYTHING_INSTANCE:填写已运行的 Everything 命名实例名称,示例为Work;使用默认实例时删除此项。它不会自动创建或启动实例。
这两项可独立使用;如果都不需要,删除整个 env。
工具
| 工具 | 功能 |
|---|---|
| everything_search | Everything 原生查询、排序和分页 |
| everything_search_exact | 完整文件名匹配 |
| everything_search_keywords | 全部/任一关键词及排除词 |
| everything_search_wildcard | * 和 ? 通配符 |
| everything_search_regex | 正则表达式 |
| everything_search_fuzzy | 连续、非连续及无序关键词匹配 |
| everything_search_pinyin | 全拼、首字母、中文混输及多音字 |
| everything_search_by_type | 文档、图片、视频、音频、代码、压缩包 |
| everything_search_typo | 文件名字符相似度匹配 |
| everything_list_directory | 直属或递归目录索引项 |
| everything_count | 匹配数量 |
| everything_status | 版本与 IPC 状态 |
例如,让客户端“查找包含合同和2025、排除草稿的 PDF”,或“按拼音 niandubaogao 搜索年度报告”。具体参数由客户端工具描述提供。
使用说明
- 默认搜索 Everything 全部索引,不额外限制目录;未索引的文件不会出现。
- 没有专门的文件内容搜索或文件修改工具。
- 拼音和容错按候选分页匹配,单页无结果不代表全盘不存在;容错分数仅在当前页排序。
- IPC 不可达时,检查 Everything 是否运行,以及客户端会话和沙箱权限。
- 终端能执行 ES 而客户端找不到时,先完全重启客户端,使其继承最新 PATH。
Metadata
Release files for evryth-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| evryth_mcp-0.1.2.tar.gz | 59.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| evryth_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.6 kB
Release files / evryth_mcp-0.1.2.tar.gz
| Download URL | evryth_mcp-0.1.2.tar.gz |
|---|---|
| Size | 59.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c04a8b0a2a859eabcd5ce9f411773ab8deca01348cdc0e05c97101e83069c5ae
|
|
BLAKE2b-256 checksum How to use checksums |
0d3222bafde73ebdf828be6531ee1a5488ce0ce59ec771d581a2b9377ef39fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / evryth_mcp-0.1.2-py3-none-any.whl
| Download URL | evryth_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0fb5739b77aeaf99a24a6bf1f26873d2c2ec6fa5e0d202f221db93005972253b
|
|
BLAKE2b-256 checksum How to use checksums |
62098130624a9bb165ebfdf23f539ddcae4a7cf1766fb01415d4eceb115d0d4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logSecurity for evryth-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for evryth_mcp-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.