World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Transactional refactoring extension with 12 evidence-backed tools, previews, and rollback.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 16/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Weavatrix Refactor,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "weavatrix-refactor": { "command": "npx", "args": [ "-y", "weavatrix-refactor", "mcp", "." ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Weavatrix Refactor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"weavatrix-refactor": {
"command": "npx",
"args": [
"-y",
"weavatrix-refactor",
"mcp",
"."
]
}
}
}用 Weavatrix Refactor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Weavatrix Refactor,或回答中出现 Weavatrix Refactor 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
WEAVATRIX_ALLOW_SOURCE_EDITS 设置为 1 可授权已确认的 apply 操作和 rollback 写入源文件;未设置时,重构工具仅为预览模式。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Weavatrix Refactor
Weavatrix Refactor 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Weavatrix Refactor 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Weavatrix Refactor,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user weavatrix-refactor -- npx -y weavatrix-refactor mcp . 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Weavatrix Refactor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user weavatrix-refactor -- npx -y weavatrix-refactor mcp .应能看到 Weavatrix Refactor 在列表中并显示已连接
用 Weavatrix Refactor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Weavatrix Refactor,或回答中出现 Weavatrix Refactor 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
WEAVATRIX_ALLOW_SOURCE_EDITS 设置为 1 可授权已确认的 apply 操作和 rollback 写入源文件;未设置时,重构工具仅为预览模式。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Weavatrix Refactor,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "weavatrix-refactor": { "command": "npx", "args": [ "-y", "weavatrix-refactor", "mcp", "." ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Weavatrix Refactor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Weavatrix Refactor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Weavatrix Refactor,或回答中出现 Weavatrix Refactor 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
WEAVATRIX_ALLOW_SOURCE_EDITS 设置为 1 可授权已确认的 apply 操作和 rollback 写入源文件;未设置时,重构工具仅为预览模式。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Weavatrix Refactor,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "weavatrix-refactor": { "type": "stdio", "command": "npx", "args": [ "-y", "weavatrix-refactor", "mcp", "." ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Weavatrix Refactor 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Weavatrix Refactor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Weavatrix Refactor,或回答中出现 Weavatrix Refactor 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
WEAVATRIX_ALLOW_SOURCE_EDITS 设置为 1 可授权已确认的 apply 操作和 rollback 写入源文件;未设置时,重构工具仅为预览模式。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user weavatrix-refactor -- npx -y weavatrix-refactor mcp .Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"weavatrix-refactor": {
"command": "npx",
"args": [
"-y",
"weavatrix-refactor",
"mcp",
"."
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"weavatrix-refactor": {
"command": "npx",
"args": [
"-y",
"weavatrix-refactor",
"mcp",
"."
]
}
}
}VS Code (mcp.json)
{
"servers": {
"weavatrix-refactor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"weavatrix-refactor",
"mcp",
"."
]
}
}
}WEAVATRIX_ALLOW_SOURCE_EDITS env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月16日
注册名称已通过 GitHub 账户 Weavatrix 验证,该账户拥有此仓库
代码最后更新于3天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 weavatrix-refactor@1.0.15 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/weavatrix-refactor)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于3天前,最新版本(1.0.15)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Weavatrix Refactor | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The explicit source-write layer of the Weavatrix ecosystem; Core remains read-only.
Refactor across files without letting the agent guess.
Weavatrix Refactor is a native MCP server for coding agents. It finds a symbol through the repository graph, previews byte-exact edits, reports every same-named occurrence it could not prove, and writes only after an explicit, hash-bound confirmation.
The useful difference is not “AI can rename a word.” It is that the agent gets evidence before the write and a recoverable transaction after it.
Run the native binary through npm:
npx -y weavatrix-refactor mcp /absolute/path/to/repository
Or install it with Cargo:
cargo install weavatrix-refactor --locked
weavatrix-refactor mcp /absolute/path/to/repository
An MCP client can start it directly. Prefer an absolute path, or Cursor's ${workspaceFolder} so the write server never follows the host process cwd:
{
"mcpServers": { "weavatrix-refactor": { "command": "npx", "args": ["-y", "weavatrix-refactor@1.0.15", "mcp", "${workspaceFolder}", "--profile=refactor"], "env": {"WEAVATRIX_ALLOW_SOURCE_EDITS": "1"} } } }
Leave WEAVATRIX_ALLOW_SOURCE_EDITS unset for preview-only sessions. Preview is a read; only a confirmed apply or rollback requires the gate. One process serves many calls at once. A call passes repository to select a child of the launch root; each child has its own graph, confirm token, and rollback, and a token from one child does not apply to another. Readers of one repository share a lock. A writer holds that lock alone, so another process receives REPO_BUSY and keeps its confirm token. Refactor does not expose Core's open_repo. A path outside the launch root needs --allow-retarget.
The repository also ships one plugin bundle for Cursor, Codex, Claude Code, and Grok Build. The plugin starts the extension-only profile, so it contributes the 12 Refactor methods without repeating Weavatrix Core's 43 read-only method definitions. Install the separate Weavatrix plugin when both surfaces are needed.
The bundled skill is optional and activates only for explicitly requested refactoring work. Its entry point stays short; each method has an individual reference card that is loaded only when needed.
Weavatrix/weavatrix-refactor marketplace from .agents/plugins, then add weavatrix-refactor@weavatrix-refactor..claude-plugin, then install weavatrix-refactor@weavatrix-refactor.grok plugin marketplace add Weavatrix/weavatrix-refactor, open /marketplace, and install it.The plugin opens WEAVATRIX_ALLOW_SOURCE_EDITS=1, but every write still needs the exact preview's short-lived, plan-bound single-use token.
For a rename task, expose only the two tools the agent needs:
weavatrix-refactor mcp /absolute/path/to/repository --profile=rename
The rename profile keeps rename_symbol and rollback_last_apply; every unrelated graph and refactor tool is absent and cannot be called. Omit the option (or use --profile=refactor) for all 12 Refactor methods. The narrower catalog reduces repeated agent context; it does not weaken preview hashes, the write gate, the confirmation token, or rollback checks.
When Weavatrix Core is already installed as a separate MCP, expose only the 12 methods that Refactor adds:
weavatrix-refactor mcp /absolute/path/to/repository --profile=refactor
The refactor profile is the default for MCP and list-tools, including the marketplace plugin. The former full compatibility profile has been removed and is rejected by both commands: Refactor no longer republishes Core methods. Install Weavatrix Core as its own MCP when read-only repository intelligence is also needed.
Suppose two files declare resolveTarget. A bare name is ambiguous, so the server refuses to pick one and returns exact ids:
// rename_symbol
{"symbol":"resolveTarget","new_name":"locateTarget","output_format":"json"}
{ "status": "NOT_FOUND", "reason": "the name matches more than one symbol; pass one of the candidate ids", "candidates": [ "symbol:src/core.ts#function:resolveTarget@2:1", "symbol:src/shadow.ts#function:resolveTarget@3:1" ] }
Retry with the intended id. The result is still read-only: it contains the edit plan, content hashes, the proven edit count, and the references the backend refused to guess at.
// rename_symbol
{ "symbol": "symbol:src/core.ts#function:resolveTarget@2:1", "new_name": "locateTarget", "output_format": "json" }
{ "status": "PLANNED", "completeness": "PARTIAL", "renamedEdits": 7, "uncertainReferences": ["... three named locations ..."], "confirmToken": "single-use-token", "plan": {"schemaVersion":"weavatrix.edit-plan.v1","files":["..."]} }
After reviewing the plan, repeat the same operation with the same inputs and its token:
// rename_symbol
{ "symbol": "symbol:src/core.ts#function:resolveTarget@2:1", "new_name": "locateTarget", "mode": "apply", "confirm_token": "single-use-token", "output_format": "json" }
{"status":"APPLIED"}
This exact flow is exercised against the real stdio MCP server. The repository fixture requires seven edits across three files, preserves four traps (a longer identifier, string, comment, and unrelated shadow), and must still compile; it scores 12/12.
The twelve tools do not all claim the same level of automation:
| Level | Tools | What the agent receives |
|---|---|---|
| Complete preview/apply workflow | rename_symbol, rename_related_symbols | A generated plan and token, then a confirmed write by repeating the same operation |
| Plan-producing | change_signature, edit_symbol, bulk_replace, organize_imports, move_file, move_symbol, delete_closure | Byte-exact edits or a review plan; use apply_edit_plan where an edit-plan envelope is returned |
| Advisory | delete_readiness | A deletion verdict. A private unused symbol can be safe: true. The verdict stays REVIEW_REQUIRED and nothing is written |
| Safety infrastructure | apply_edit_plan, rollback_last_apply | Verification/application of an edit-plan envelope and drift-safe restoration |
Refactor uses the Rust Weavatrix graph internally for evidence but never exports Core methods. Install the separate Weavatrix plugin for read-only repository intelligence. The Refactor MCP owns exactly its 12 extension methods; --profile=rename is an optional narrower two-method workflow.
PARTIAL means the graph proved the edits in the plan but did not prove that no other semantic references exist. uncertainReferences names the places requiring review.WEAVATRIX_ALLOW_SOURCE_EDITS=1 plus a short-lived, single-use token bound to that repository and exact recomputed plan.rollback_last_apply refuses to overwrite files that drifted after the transaction.REPO_BUSY until the call finishes. The confirm token stays usable.Only edits with proven provenance are applied. A lexical or graph backend is deliberately more conservative than a language server and must not be read as a claim of full compiler semantics.
The default profile exposes these twelve methods. --profile=rename keeps only rename_symbol and rollback_last_apply. A planning method returns an edit plan. apply_edit_plan is the write for every plan except the two rename methods, which apply themselves when mode is "apply".
rename_symbolRenames one symbol from the graph. A bare name that matches more than one symbol returns NOT_FOUND and the candidate ids. The preview lists the declaration and every call or reference the graph proves, plus import lines of files the graph proves import the declaring file. A same-named occurrence the graph does not prove stays in uncertainReferences and is left unchanged. Completeness stays PARTIAL. Repeat the same symbol and new_name with mode:"apply" and the preview token to write. A missing source span is NOT_A_SYMBOL. A route label is renamed as a path literal.
rename_related_symbolsRenames several symbols in one transaction. The sites are the same ones rename_symbol can prove, in every indexed language. Two symbols given one new name, or two edits of the same site, return CONFLICT. A chain or a swap is applied together and reported in ordering. Completeness stays PARTIAL. Preview returns the token; mode:"apply" with that token writes the whole batch.
change_signaturePlans an added or removed parameter in every indexed language. Kotlin is read with the Java tokenizer. A typed language copies the previous parameter's type. When the new parameter has a default, existing calls stay. Without a default, proven calls are edited when the call supplies a value. A call the graph missed is edited only when that name is declared once and its argument list can be read; otherwise the call is listed. The result stays PARTIAL. Spread arguments are reported and left unchanged. Apply the returned plan with apply_edit_plan.
edit_symbolPlans a replacement or insertion inside one declaration. The range runs from the declaration through the matching brace or the indent block. When only the signature line can be located, the plan is PARTIAL and warns DECLARATION_END_UNPROVEN. Every plan warns that syntax was not checked. Apply it with apply_edit_plan.
bulk_replacePlans a literal or regular-expression replacement over indexed code, in two stages: list the occurrences, then plan the ones you accept. Comments and strings are included only when include_trivia is true. An extension the tokenizer does not know still skips // comments, block comments, quotes, and a # that starts a line. The caps are 5000 files, 500 matches in one file, and 5000 matches in the plan. Apply the plan with apply_edit_plan.
organize_importsPlans removal of a named binding whose identifier occurs once in the file. A Rust snake_case use, a Python from import or alias, a Go path segment, a Java import, a C# using, a C++ using name, and a Kotlin import are removed when that is true. A CamelCase Rust import such as use std::io::Write, a pub use, a bare Python import, a Go blank or dot import, a star import, a C++ #include, and a using namespace stay. JavaScript and TypeScript default and namespace imports stay uncertain. A file whose extension has no recognised import syntax returns NO_UNUSED_IMPORTS. Apply the plan with apply_edit_plan.
move_filePlans the filesystem rename and the relative import rewrites in one transaction. A missing parent directory is created at a