FTX MCP — FactoryTalk Optix MCP Server

io.github.asqi-carter由 GitHub 账号 asqi-carter 发布v1.0.9更新于 Oct 28, 2026

MCP server for FactoryTalk Optix: author, preview, and verify Studio changes via the emulator.

已验证STDIO仅桌面浏览器自动化开发者工具

概览

AI 生成的概览

将 AI 助手连接到 Windows 上的 FactoryTalk Optix Studio,可编写 HMI 画面、运行仿真器并验证效果。

可以做什么
  • 在打开的 Studio 项目中编写控件、属性、绑定、计算表达式、事件、翻译和多画面导航
  • 运行 Studio 内置仿真器并读取运行时日志
  • 通过截图、点击按钮和标签页、在输入框中输入来验证运行时画面
  • 用 OCR 模式读取运行时文本,替代截图
  • 发现并加载内置的编写指南
  • 检查环境健康状况,并通过桥接读写项目文件
适用场景
适合在 FactoryTalk Optix Studio 中制作 HMI 或 SCADA 画面时使用,让助手直接修改画面、在仿真器中预览并确认效果,再由你自己部署到硬件。
运行要求
Windows 11、FactoryTalk Optix Studio 1.7.x、Python 3.12,并通过安装脚本或 pip 包在本地安装。build_check 需要 .NET SDK 8 或更高版本,验证流程需要 Google Chrome,文本工具会安装 Tesseract OCR。每个项目需在 Studio 中添加并启动 DesignTime NetLogic 桥接,每个 Studio 会话都要启动一次。仅 Claude Desktop 商店版连接方式需要 Node.js。
安装前请注意
助手会直接写入你打开的 Studio 项目,改动是真实编辑;每次修改都会写入本地审计日志,组合操作失败时会回滚。默认安装仅绑定本机回环地址且不启用认证,绑定到局域网则必须启用 bearer 令牌认证。部署到硬件仍由你在 Studio 中完成。安装脚本会通过 winget 安装软件,并可能需要在当前会话中放宽 PowerShell 执行策略。

安装

在 SourceWeft 中

  1. 打开 控制台中的 FTX MCP — FactoryTalk Optix MCP Server,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

ftx-mcp

Talk to your FactoryTalk Optix project. ftx-mcp connects AI tools (Desktop, Cowork, Code — or any MCP client) to FactoryTalk Optix Studio on your Windows machine, so you can build and change HMI screens by describing what you want:

"Add a header that says 'Hello Optix' to Screen 1 and show me."

"Bind that label's visibility to Model/PumpRunning."

"Looks right. Launch the emulator and validate it."

Your LLM authors the change directly into your open Studio project, runs the emulator, and looks at the rendered runtime to confirm it worked. It is a development and testing companion: shipping to hardware stays in Studio's own Deploy dialog, in your hands. Everything besides the LLM calls runs locally on your machine. No cloud service, no API key; your LLM of choice provides the intelligence.

Blog Post

Install (10 minutes)

Requirements: Windows 11, FactoryTalk Optix Studio 1.7.x, and an MCP client like Claude Cowork. Also: the .NET SDK (8 or later), needed for build_check (without it build_check returns no_dotnet); Google Chrome (the CDP verify loop; skip with setup.ps1 -NoCdp) and — for the Claude Desktop Microsoft Store build connector path — Node.js (winget install OpenJS.NodeJS.LTS; the config uses npx mcp-remote). Setup auto-installs Tesseract OCR via winget for the zero-vision-token text tools (skip with -NoOcr; everything else works without it) and Pillow (a hard dependency) into the venv for pixel diffing.

Run setup.ps1 from a regular PowerShell window — not a shell hosted inside a packaged app like the Store build of Claude Desktop, whose %LOCALAPPDATA% writes are virtualized (setup now detects this and refuses). If you downloaded a ZIP instead of cloning, run Get-ChildItem -Recurse | Unblock-File first.

If setup.ps1 (or any bootstrap\*.ps1) fails to run at all with a script- execution / "running scripts is disabled" error, your machine's execution policy is blocking unsigned scripts. Unblock them for the current window only — no admin, no persistent policy change — then re-run:

powershell
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
powershell
git clone https://github.com/asqi-carter/ftx-mcp.gitcd ftx-mcp.\bootstrap\setup.ps1                                  # install (does not start anything).\bootstrap\services.ps1 start                         # start the service + cdp chrome.\bootstrap\services.ps1 status                        # verify healthhttp://127.0.0.1:8765/ui                               # health dashboard

Auth: the default install is loopback-only with auth OFF — setup never prompts, and no token is needed on your own box. Binding to the LAN is the one case that requires auth: install with .\bootstrap\setup.ps1 -EnableAuth (see docs/security.md). If a UI/API unexpectedly asks for a bearer token, a previous install enabled auth — re-run setup with -NoAuth to clear it.

To remove an install (or reset before a clean reinstall): .\bootstrap\uninstall.ps1 stops and unregisters the scheduled tasks and reaps any leftover CDP chrome; add -All to also delete state (issued tokens, chrome profile, persisted auth choice) and the venv.

pip / registry install

pip install ftx-mcp installs the service and its dependencies (including Pillow, now a hard dependency; ftx-mcp[visual] is kept as an empty extra for older instructions). The wheel also carries the authoring skills (skills/*/SKILL.md), the Studio bridge source (StudioMCPBridge.cs) and the /ui dashboard, so the skill tools and optix_bridge_arm bridge sync work without a checkout; a checkout install keeps reading the repo's skills/ and studio-bridge/.

What you do not get from pip, and still do by hand (see docs/runbook.md): Studio, Tesseract OCR, Chrome for the CDP loop, the scheduled tasks / service registration, auth setup and the BridgeTemplate refresh. bootstrap\setup.ps1 from a checkout remains the supported Windows install.

To get the bridge source for a project or template when you have no checkout, fetch it from the running service:

powershell
Invoke-WebRequest http://127.0.0.1:8765/bridge-source -OutFile StudioMCPBridge.cs

GET /bridge-source returns the shipped file as text/plain with an X-Ftx-Mcp-Version header.

Upgrading

To upgrade a checkout install (e.g. 1.0.8 → 1.0.9), run these five steps, in order, from a regular PowerShell window in the checkout:

  1. bootstrap\services.ps1 stop
  2. git pull (or replace the checkout)
  3. bootstrap\uninstall.ps1 -PurgeVenv
  4. bootstrap\setup.ps1
  5. bootstrap\services.ps1 start

Your state, secrets and logs live in %LOCALAPPDATA%\ftx-mcp\ and survive the procedure (-PurgeVenv removes only the virtualenv).

  • Existing projects: the first optix_bridge_arm on each existing project syncs its bridge source to the shipped version and leaves a backup of the previous one under ProjectFiles\.ftx-mcp-backups\.
  • BridgeTemplate: refresh a registered BridgeTemplate with the manual copy steps in docs/runbook.md. Projects made from an old template are synced on their first arm.
  • pip install --upgrade is not a supported route. It does not upgrade a checkout install: it can bump the pip-reported version while the service keeps running the checkout's code. Use the five steps above.

See also docs/release-notes-v1.0.9.md.

Start the Studio Bridge (5 minutes)

  1. One-time bridge setup (per project): in the Studio project tree, right-click NetLogic → add a new DesignTime NetLogic named StudioMCPBridge, double-click it to open the C# editor, and paste in studio-bridge/StudioMCPBridge.cs (make sure to rebuild in your code editor or save in Studio to trigger a rebuild)
  2. Setup the Project once per Studio session: right-click StudioMCPBridge → SetupProject → This just adds a webui for validation access at localhost:8081
  3. Start the bridge once per Studio session: right-click StudioMCPBridge → StartBridge → accept Studio's one-time security prompt.
  4. Verify bridge health: Studio Output will show listening on http://127.0.0.1:8768 (the bridge). The service dashboard at http://127.0.0.1:8765/ui shows bridge status too.

Cowork (5 minutes)

Requirements: MCP server and bridge running. Claude desktop app downloaded.

powershell
cd ftx-mcp                   # install + start the service.\bootstrap\setup-mcp-client.ps1 -WriteConfig          # adds as a connector to desktop app

Restart Claude Desktop (You might have to end task in task manager to fully restart), then ask Claude to "run optix_status(action='doctor')" — it reports anything missing, with a plain-English fix for each item. In settings > connectors you can adjust the permissions for each of the tools

Claude Code (5 minutes)

ftx-mcp serves MCP over streamable-HTTP at http://127.0.0.1:8766/mcp.

Requirements: MCP server healthy and claude accessible in cli

powershell
claude mcp add --transport http ftx-mcp http://127.0.0.1:8766/mcp

Then in Claude Code, run /mcp and confirm ftx-mcp shows as connected.

Visual Studio Code (5 minutes)

Create or open .vscode/mcp.json and add:

json
{  "servers": {    "ftx-mcp": {      "type": "http",      "url": "http://127.0.0.1:8766/mcp"    }  }}

Your first change

  1. Ask for a change, e.g. "Using the ftx mcp, Add a Start and stop button that toggles Model/MotorRun on MainWindow, and verify it works with a label with the text of 'MOTOR RUNNING' that has visibility tied to MotorRun."
  2. Watch it work: author → emulator preview → screenshot → and when it looks right, you deploy it to your hardware from Studio as usual.

What it's capable of

  • Author widgets, properties, bindings, computed expressions, events, translations, and multi-screen navigation — live in the open Studio project.
  • Run Studio's built-in emulator via F5 key and read the runtime log.
  • Verify by looking at the webui: screenshot, click buttons and tabs, type into fields.
  • Hand back to you to ship when the preview looks right, you deploy from Studio as usual. This distribution only runs the emulator.

The full tool list (36 tools by default — gate env vars can add more — plus the same surface over plain HTTP for scripts and CI) is in docs/tool-reference.md. Token economy: screenshots cost ~1-2k vision tokens each; the OCR modes of optix_observe (read_text, find_text, diff) turn most checks into free text reads — see the optix-blind-authoring and optix-visual-regression playbooks for the workflow (setup installs tesseract automatically; -NoOcr opts out).

Bundled 19 authoring playbooks (navigation, bound controls, styles, expressions) ship with the server itself — Claude discovers them via optix_list_skills / optix_get_skill, so every connected client gets them with zero setup. (In Claude Code they also load natively as skills.)

Security & safety posture

  • Local only. The service binds 127.0.0.1 and talks to nothing off the machine. Optional bearer-token auth, enforced before any LAN bind.
  • Read-only by default. Every tool carries MCP readOnlyHint / destructiveHint annotations (contract-pinned by tests) so your MCP host can auto-approve reads and gate writes.
  • Write gates, not hope. Undeclared properties, array writes, duplicate names, and unsafe re-parents are refused with typed errors; composite operations roll back on failure. Project file reads (optix_read_file) are refused while Studio has the project open; live-model reads and writes go through the bridge.
  • Audited. Every model mutation appends a JSON line to a local audit trail (%LOCALAPPDATA%\ftx-mcp\logs\audit.jsonl) what, when, outcome.
  • Shipping stays in your hands. Previewing never touches your runtime; deploying to hardware happens from Studio, full stop. This distribution does design time edits and testing via the emulator.

The full posture including the prompt-injection surface analysis is in SECURITY.md.

Documentation

RunbookFirst session, step by step
Tool referenceEvery MCP tool + the HTTP API
ArchitectureHow the pieces fit together
TroubleshootingSymptom-indexed fixes
SecurityAuth, ports, what talks to what

Compatibility

Tested with FactoryTalk Optix Studio 1.7.x on Windows 11, Python 3.12. Optix CLI behavior is not contract-stable across major versions — pin your Studio version in production.

License

MIT · © 2026 ASQI · Not affiliated with or endorsed by Rockwell Automation. FactoryTalk Optix is a trademark of Rockwell Automation, Inc.; this project orchestrates locally installed Optix binaries without redistributing them. See NOTICE.

来源:README.md,提交 4df5384

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

3
  1. v1.0.9最新Oct 15, 2026
  2. v1.0.8Oct 1, 2026
  3. v1.0.7Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。