
FTX MCP — FactoryTalk Optix MCP Server
io.github.asqi-carterPublished by GitHub account asqi-carterv1.0.9Updated Oct 28, 2026
MCP server for FactoryTalk Optix: author, preview, and verify Studio changes via the emulator.
Overview
Connects an AI assistant to FactoryTalk Optix Studio on Windows so it can author HMI screens, run the emulator and verify the result.
- What you can do
- Author widgets, properties, bindings, computed expressions, events, translations and multi-screen navigation in the open Studio project
- Run Studio's built-in emulator and read the runtime log
- Verify the rendered runtime by screenshot, clicking buttons and tabs, and typing into fields
- Read text from the runtime with OCR modes instead of screenshots
- Discover and load bundled authoring playbooks
- Check environment health and read or write project files through the bridge
- When to use it
- Useful when you build HMI or SCADA screens in FactoryTalk Optix Studio and want an assistant to make changes, preview them in the emulator and confirm they look right before you deploy to hardware yourself.
- Requirements
- Windows 11 with FactoryTalk Optix Studio 1.7.x, Python 3.12 and a local install via the setup script or the pip package. The .NET SDK 8+ is needed for build checks, Google Chrome for the verification loop, and Tesseract OCR is installed for text tools. A per-project Studio bridge (DesignTime NetLogic) must be added and started each Studio session. Node.js is only needed for the Claude Desktop Store connector path.
Installation
In SourceWeft
- Open FTX MCP — FactoryTalk Optix MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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.
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:
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:
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:
bootstrap\services.ps1 stopgit pull(or replace the checkout)bootstrap\uninstall.ps1 -PurgeVenvbootstrap\setup.ps1bootstrap\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_armon each existing project syncs its bridge source to the shipped version and leaves a backup of the previous one underProjectFiles\.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 --upgradeis 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)
- 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 instudio-bridge/StudioMCPBridge.cs(make sure to rebuild in your code editor or save in Studio to trigger a rebuild) - Setup the Project once per Studio session: right-click StudioMCPBridge → SetupProject → This just adds a webui for validation access at localhost:8081
- Start the bridge once per Studio session: right-click StudioMCPBridge → StartBridge → accept Studio's one-time security prompt.
- 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.
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
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:
Your first change
- 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."
- 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.1and talks to nothing off the machine. Optional bearer-token auth, enforced before any LAN bind. - Read-only by default. Every tool carries MCP
readOnlyHint/destructiveHintannotations (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
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.
Source: README.md at commit 4df5384
Tools
0Version history
3- v1.0.9LatestOct 15, 2026
- v1.0.8Oct 1, 2026
- v1.0.7Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.