MCP serverCommunity
CAD Agent Hubby Cai-aa
Separate Windows MCP servers for CATIA V5, Siemens NX and SOLIDWORKS, kept in one repository with test scripts.
LocalWindowsNeeds a Siemens NX licenceCan modify models134· updated 2 days ago
Siemens NX MCP servers and AI agent skills
Siemens NX is reached through community MCP servers only. Each one loads code into NX through NX Open, either a signed .NET plug-in or a Python journal, and an outside stdio server relays the agent's calls, so everything runs on the Windows workstation where NX is licensed. Coverage ranges from basic sketches and extrudes to assemblies, sheet metal, drafting and a CAM foundation. A separate server searches the NXOpen API documentation from your own installation. Siemens has not released an NX MCP server.
- No official Siemens server yet.
- 4 MCP servers listed.
Siemens4 serversChecked 4 Nov 2026
Integrations for Siemens NX
Community and commercial servers
MCP serverCommunity
NX MCP (DreamEnding)by DreamEnding
A Python sidecar plus an NX bridge (C# GUI or Python batch) with 16 typed tools for parts, sketches and STEP.
LocalWindowsNeeds a Siemens NX licenceCan modify models159· updated 3 weeks ago
MCP serverCommunity
nx-auto-mcpby cyw2527
A Node.js stdio adapter and signed NXOpen plug-in exposing 130+ NX modelling, sketch, assembly and measure tools.
LocalWindowsNeeds a Siemens NX licenceCan modify models10· updated 7 weeks ago
MCP serverCommunity
nxopen-mcpby mingfeng6684
Searches the NXOpen .NET API docs from your own NX install, so coding agents stop inventing NXOpen calls.
LocalWindowsNeeds a Siemens NX licenceRead-only19· updated 4 months ago
Listings are sorted by origin, then by recent activity. GitHub data is refreshed nightly. Nothing here is ranked.
How AI connects to Siemens NX
An MCP server or skill can only do what Siemens NX lets programs do. Siemens NX exposes 2 automation interfaces:
- NX Open (.NET, Python journals) (.NET): NX Open is the programming layer every NX server here depends on. Journals run through NX's journal player or run_journal.exe, which suits batch work but blocks while running; resident plug-ins stay loaded and answer calls quickly, but NX only loads .NET DLLs that are signed with SignDotNet.exe or run under an NX Open .NET author licence. Version matters: listed projects target NX 2206, 2412 or 2506. Siemens' NX Open reference sits in its Support Center, which needs a sign-in. Documentation
- NXOpen API reference (local XML docs) (Other): An NX installation ships NXOpen XML documentation and assemblies under UGII\managed. The nxopen-mcp server indexes those files so a coding agent can look up real classes and methods before writing journal code, which matters because public training data on NXOpen is thin and models tend to invent calls.
What Siemens offers
Siemens builds AI into NX itself. Copilot in Designcenter X NX (formerly NX) is a chat assistant that gives step-by-step guidance with cited sources and links to commands, and it considers recent commands but not personal data. Siemens' blog describes guidance, not automatic command execution, and does not mention MCP or outside AI clients. Siemens runs a public MCP server at mcp.siemens.com, but it searches siemens.com and developer content, not NX models.
Checked 4 Nov 2026. Sources: Siemens Designcenter blog, NX tips and tricks, Copilot (12 May 2026), Siemens MCP Server documentation
What you can do with Siemens NX and AI
- Create a part, sketch a profile and extrude it, then list bodies and features and export STEP.
- Build assemblies with fix, touch, concentric and distance constraints and read back the solver status.
- Make sheet-metal tabs, flanges and bends and export a flat pattern as DXF.
- Place drafting views and associative linear dimensions on a drawing sheet.
- Set up a CAM milling context with tools and operations as a starting point for programming.
- Look up exact NXOpen .NET classes and methods from your installation's docs before writing a journal.
Taken from the listings' own documentation. Check each listing for exactly what it supports.
Installing
The listings here document setup for Claude, Claude Code, Codex and Cursor. Install steps, copied from each project's own documentation, are on each listing's page. Most Siemens NX integrations run on your own computer next to Siemens NX, so you need Siemens NX installed and licensed on the same machine unless the listing says otherwise.
Related tools
Questions
Is there an official Siemens NX MCP server?
No, not as of 4 November 2026. Siemens offers Copilot inside Designcenter NX for guidance, and its public MCP server at mcp.siemens.com searches Siemens web and developer content. Every NX server listed here is a community project.
Can Claude or Codex control Siemens NX?
Yes, with a community server. You load a bridge into NX (a signed .NET plug-in or a Python journal), start NX with a part open, and register the server's stdio command in your client. The agent's calls are then executed through NX Open in your session.
Which NX versions are supported?
Each project names its own: one documents NX2206 for its GUI bridge and NX2506 for its batch bridge, and two others were developed against NX 2412. API differences between releases can break tools, so run each project's diagnostics on your version first.
Why do NX bridges need signing or an author licence?
NX loads unsigned .NET DLLs only with an NX Open .NET author licence. Without it, you sign the plug-in yourself with NX's SignDotNet.exe, which is why one project ships source only and builds on your machine.
AI-generated models, drawings and results must be checked by a qualified engineer before use.
Sources (checked 4 Nov 2026): DreamEnding/NX_MCP README · cyw2527/nx-auto-mcp README · Siemens Designcenter blog, NX tips and tricks, Copilot · Siemens NX product page
Siemens NX is a trademark of Siemens. Tresca is independent and not affiliated with or endorsed by Siemens.