World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
MCP gateway for Autodesk Navisworks Manage 2022-2027.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 13/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 25/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Bimwright NWD。按照 https://mcp.popnx.com/i/bimwright-nwd-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月16日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Bimwright NWD,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "nwd": { "command": "dnx", "args": [ "Bimwright.Nwd.Server", "--yes" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Bimwright NWD 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
SettingsDeveloperEdit Config
{
"mcpServers": {
"nwd": {
"command": "dnx",
"args": [
"Bimwright.Nwd.Server",
"--yes"
]
}
}
}用 Bimwright NWD 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Bimwright NWD,或回答中出现 Bimwright NWD 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Bimwright NWD
Bimwright NWD 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Bimwright NWD 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
不需要密钥,不用安装程序
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Bimwright NWD,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user nwd -- dnx Bimwright.Nwd.Server --yes 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Bimwright NWD 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user nwd -- dnx Bimwright.Nwd.Server --yes应能看到 Bimwright NWD 在列表中并显示已连接
用 Bimwright NWD 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Bimwright NWD,或回答中出现 Bimwright NWD 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
不需要密钥,不用安装程序
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Bimwright NWD,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "nwd": { "command": "dnx", "args": [ "Bimwright.Nwd.Server", "--yes" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Bimwright NWD 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
用 Bimwright NWD 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Bimwright NWD,或回答中出现 Bimwright NWD 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
不需要密钥,不用安装程序
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Bimwright NWD,按顺序:1) 2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "nwd": { "type": "stdio", "command": "dnx", "args": [ "Bimwright.Nwd.Server", "--yes" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Bimwright NWD 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
用 Bimwright NWD 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Bimwright NWD,或回答中出现 Bimwright NWD 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user nwd -- dnx Bimwright.Nwd.Server --yesClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"nwd": {
"command": "dnx",
"args": [
"Bimwright.Nwd.Server",
"--yes"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nwd": {
"command": "dnx",
"args": [
"Bimwright.Nwd.Server",
"--yes"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"nwd": {
"type": "stdio",
"command": "dnx",
"args": [
"Bimwright.Nwd.Server",
"--yes"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 bimwright 验证,该账户拥有此仓库
代码最后更新于4天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/bimwright-nwd-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于4天前,最新版本(1.1.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 .NET。
同一分类中有: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. 100 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.
| 本项 Bimwright NWD | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
nwd-mcp
English · Tiếng Việt · 简体中文 · 日本語
nwd-mcp is a professional-grade Model Context Protocol (MCP) gateway for Autodesk Navisworks Manage automation. It enables AI agents to query, inspect, navigate, and script Autodesk Navisworks Manage desktop sessions locally over stdin/stdout.
.NET 8 console server communicating with a version-specific in-process plug-in. Wire transport is TCP NDJSON over loopback for every supported year (2022–2027); all six plug-in shells target .NET Framework 4.8 / net48. (Unlike the rest of the bimwright family, nwd-mcp does not use Named Pipe transport — the loopback-TCP convention applies uniformly across all versions.)AMBIGUOUS_TARGET. If the bound instance exits, commands return TARGET_LOST or TARGET_CHANGED (not sent) until you confirm a target with nwd_switch_target. Selectors are pid: , id: , a year 2022–2027, or auto. When several agents or same-year instances run, call nwd_list_available_targets (it shows pid and window_title) and pin nwd_switch_target("pid: ") at session start. A year or auto never moves an existing binding (TARGET_REBIND_REQUIRED), and leaving a live, explicitly chosen instance needs rebind=true. nwd_list_available_targets and nwd_get_current_target never select a target. Writes run only on a confirmed document: check with the user that the reported file is the one to change, then call nwd_switch_target("pid: ", verify=true) once. Until then writes return TARGET_UNCONFIRMED; if another file was opened since, DOCUMENT_CHANGED (the command did not start). nwd_open_file moves the confirmation to the file it opens. A server and plug-in from different releases return PAIRING_REQUIRED for writes; reads still work.HOST_BUSY: it was not started and will not run later, so it is safe to send again once Navisworks is free. TIMEOUT now means the command started and its outcome is unknown: inspect before retrying a write. nwd_health_check still answers while Navisworks is busy, with host_busy and busy_reason (modal_dialog or ui_thread_busy).Navisworks shows one activity card for MCP commands. Toasts are on by default and stay up for 20 seconds after the latest result (10, 20, 30, or 60). Hover pauses the card; leaving it starts the selected interval again. A deliberate hover smoothly expands a compact three-row view of the current card's individually bordered outcomes (tool, result, success/failure and local completion time in 24-hour HH:mm:ss). Every outcome in that card is retained, oldest above newest; the view starts at the latest three, and scrolling up reaches earlier calls through a thin RVT-style scrollbar. Leaving smoothly collapses it. Incoming outcomes appear immediately: at the bottom, the view follows the newest calls; while reading older calls, it preserves your scroll position. Returning to the bottom resumes following. The preview works with branding off and respects reduced motion. These length-limited summaries live only in memory and are discarded when the card closes or resets; they do not enable Record or retain raw requests, response JSON or script source. The BIMwright wordmark stays off unless Show branding is turned on. nwd_health_check does not appear on the card. The Bimwright ribbon tab has Toasts, Toast Brand, Record, and Status. Record supplies the host default for legacy gateways; current gateways use the server call-log setting described below. send_code is stored as a length and SHA-256, not the script. Settings live in %LOCALAPPDATA%\Bimwright\nwd-mcp\nwdmcp.config.json. BIMWRIGHT_NWD_ENABLE_TOAST and BIMWRIGHT_NWD_RECORD_CALLS override those switches at the next launch.
Status → toast position: choose horizontal Left/Right and vertical Top/Bottom independently (default: top-left). Changes apply and save immediately; changing the corner clears any saved drag offset. Enable Allow dragging the toast to drag its title row; a normal click still dismisses the card. Disabling drag returns to the selected corner without deleting the saved position; re-enabling restores it. Reset position removes the offset. Positions are stored relative to the Navisworks window in DIP and clamped to its monitor's work area. Bottom anchors expand upward; if space is insufficient, expansion uses the opposite side. Motion respects the Windows animation setting. A save failure is reported inline in Status while the new preference remains active for this session. Latest-tool and outcome tooltips include the sanitized result, status, completion time and measured duration when available. This does not coordinate overlapping toasts from different apps.
| Component | Status |
|---|---|
| MCP gateway server (.NET 8) | ✅ Builds warning-clean (Debug + Release) |
| Unit tests (155 xUnit) | ✅ All passing |
| Plug-in handler implementations | ✅ Verified against a live Navisworks Manage session |
| Plug-in projects (net48) | ✅ Compile against the Navisworks Manage SDK |
Note: The plug-in handler layer uses real Navisworks .NET API calls (not stubs or fabricated
data) and has been exercised against a live Navisworks Manage instance.
The first-run checklist is docs/testing/manual-smoke.md.
Download the client setup ZIP from GitHub Releases. It includes a self-contained MCP server and the Navisworks Manage plugin years compiled for that release (see manifest.json). The v1.0.0 ZIP ships 2025 only. Other years: build from source against that year’s Manage SDK.
$tag = (Invoke-RestMethod https://api.github.com/repos/bimwright/nwd-mcp/releases/latest).tag_name
$zip = "$env:TEMP\NwdMcp.Setup-$tag-win-x64.zip" $dir = "$env:TEMP\NwdMcp.Setup-$tag-win-x64" Invoke-WebRequest "https://github.com/bimwright/nwd-mcp/releases/download/$tag/NwdMcp.Setup-$tag-win-x64.zip" -OutFile $zip Expand-Archive $zip -DestinationPath $dir -Force
powershell -ExecutionPolicy Bypass -File "$dir\install.ps1" -WhatIf powershell -ExecutionPolicy Bypass -File "$dir\install.ps1"
Deploys %APPDATA%\Autodesk\ApplicationPlugins\Bimwright.Nwd.bundle\ and nwd-mcp.exe at the fixed path %LOCALAPPDATA%\Bimwright\nwd-mcp\server\current\. Restart Navisworks Manage. Point your MCP client at that nwd-mcp.exe path. Pin a year with --target 2025 or BIMWRIGHT_NWD_TARGET=2025 when multiple instances may run.
The NuGet package Bimwright.Nwd.Server is server-only: it has no Navisworks plug-in. Install from the setup ZIP; use dotnet tool install -g Bimwright.Nwd.Server only if the plug-in is already installed from the ZIP and you want the server as a global .NET tool (command bimwright-nwd).
Developer: dotnet build a plugin-navisNN project, then pwsh scripts\install-bundle.ps1 -Year 2025 -Configuration Release.
Useful flags after wiring: --read-only / BIMWRIGHT_NWD_READ_ONLY=1.
A default launch registers every toolset: 35 tools. --read-only leaves 25. Every tool uses the nwd_* prefix.
nwd_list_available_targets — List all active discovered Navisworks sessions.nwd_get_current_target — Report which session the server is currently pointed at.nwd_switch_target — Point the gateway at a different active session; verify=true also confirms the open document for writes.nwd_report_task_result — Report a finished job once (completed, failed or cancelled, one-line summary, optional Markdown body): a card on the Navisworks toast and a saved report. Agent-reported, not verified. Responses of document writes carry _report until you do.nwd_get_report_history — Read saved reports from %LOCALAPPDATA%\Bimwright\nwd-mcp\reports, newest first, or one in full by report_id.nwd_list_recent_files — List recent files for the running Manage year, in File menu order.nwd_open_file *(Write)* — Open a file. Refuses while the current file has unsaved changes unless discard_changes is true.nwd_import_model *(Write)* — Bring a model into the open document. append (default) adds it; merge combines it.nwd_health_check — Probe host/document state and loaded server/plugin versions, build ids and alignment. Offline by default; optional check_updates=true compares both components with the latest official stable release and tag revision. No host still returns server identity with ok:false, host_connected:false.nwd_get_document_info — Retrieve active document name, file path, and model count.nwd_get_model_statistics — Retrieve counts of elements, models, and selections.nwd_get_model_tree — Retrieve a bounded model tree node hierarchy.nwd_get_item_properties — Retrieve property categories and property lists for an element.nwd_batch_get_properties — Retrieve properties for multiple elements at once.nwd_find_items — Query elements using advanced property/category filters.nwd_find_items_by_name — Search elements by display name.nwd_get_current_selection — Retrieve element IDs of the active user selection.nwd_clear_selection *(Write)* — Clear the active selection.nwd_select_items_by_search *(Write)* — Select items matching property/name filters.nwd_list_sets — Retrieve selection and search sets, recursing folders.nwd_get_selection_set_items — Retrieve elements inside a set.nwd_execute_search_set *(Mixed)* — Execute a search set; optionally select matches.nwd_list_viewpoints — Enumerate saved viewpoints and folders.nwd_get_current_viewpoint — Retrieve current camera and view state.nwd_goto_viewpoint *(Write)* — Navigate the viewport camera to a saved viewpoint.nwd_save_viewpoint *(Write)* — Save the active view as a named viewpoint.nwd_hide_items *(Write)* — Hide/show specified elements.nwd_unhide_all *(Write)* — Reset all hidden elements to visible.nwd_send_code *(Write)* — Run