nxopen-mcp
MCP serverCommunity
Searches the NXOpen .NET API docs from your own NX install, so coding agents stop inventing NXOpen calls. By mingfeng6684.
19 starsUpdated 4 months agoGitHub data from 5 Nov 2026
At a glance
- Type
- MCP server
- Works with
- Siemens NX
- How it connects
- Documentation only; doesn't operate the tool
- Access
- Read-only
- Tool versions
- Indexes the NXOpen XML docs of your installed NX (example uses NX 12.0)
- Operating systems
- Windows
- Needs a Siemens NX licence
- Yes
- Transport
- Local (stdio)
- AI clients documented
- Claude Code, Codex, Cursor
- Licence
- MIT
- Language
- Python
What it can do
- Builds a local index from the NXOpen*.xml documentation and assemblies in your NX installation.
- Answers natural-language queries in English or Chinese with semantic search, and pins exact class or method names to the top.
- Shows inherited members of a class when the optional pythonnet extra is installed.
- Runs offline; no Siemens files are bundled or uploaded.
Limitations
- Does not drive NX; it only grounds code the agent writes.
- Indexing a full NX 12 doc set can take several hours on a laptop CPU and downloads a ~2 GB embedding model.
Install
pip install "nxopen-mcp[embed,reflect]"
nxopen-mcp index --nx-path "D:\Siemens\NX12.0"
claude mcp add -s user nxopen -- nxopen-mcp serveMCP servers and skills run code on your computer. Review the source before installing.
AI-generated models, drawings and results must be checked by a qualified engineer before use.