DNK MCP Creo
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
DNK MCP Creo
A Model Context Protocol server for PTC Creo Parametric.

DNK MCP Creo connects MCP clients such as Claude Desktop, Codex, opencode, and Cursor to a live PTC Creo Parametric session. It uses a thin, out-of-process C++ Object TOOLKIT (OTK) bridge and a typed TypeScript server, so an agent can inspect a model, export it, author real solid features, and generate drawings — with every write guarded, verified, and audited.
Status: 0.1.0 — first public release. 65 tools across 6 packs (core plus 5 opt-in), 122 mock tests, and live verification against Creo Parametric 9.0.2.0. The implementation covers milestones M1–M5 partially; see docs/ROADMAP.md for exactly what is done and what is not.
What it does
Capability | Examples |
Inspect | Session and working directory, open models, parameters, dimensions, features, relations, mass properties, materials, layers, units, geometry, edges, surfaces, family tables |
Export | STEP, IGES, STL (ASCII/binary), drawing PDF, DXF |
Model | Save, rename, copy, regenerate, parameters, dimensions, suppress/resume/delete/reorder features, create parts and assemblies, assemble components, part from template |
Author geometry | Extrude, revolve, round, chamfer, shell, datum plane/axis/point, straight and counterbored/countersunk holes, linear and axis-driven patterns, feature-tree readback |
Draw | Create drawings from templates, add sheets and views, generate a standard drawing with optional PDF/DXF, save |
Stay safe | Read-only by default, pack gating, path containment, value guards, copy-modify-verify, rollback, JSONL audit |
The showcase part above is built end to end by
scripts/build-showcase-model.mjs: a
six-spoke pulley with a Ø160 rim, six cut windows, a Ø24 keyed bore, and
volume-verified geometry.
Related MCP server: creo-mcp-server
Why this design
Out-of-process async OTK bridge. No code is loaded into Creo, the undo stack is left alone, and the bridge can change without restarting Creo.
Thin bridge, smart server. Safety policy, guards, copy-modify-verify, allowlists, and audit live in TypeScript. Adding a rule never requires recompiling C++.
Versioned framed protocol. Every bridge line carries a
__CREOBRIDGE__prefix, so stray PTC output cannot corrupt the JSON stream.Small context, explicit capability. Packs are opt-in (except
core). The agent sees only the tools you enable, not all 65.
Architecture

MCP clients (Claude, Codex, opencode, Cursor)
| stdio (JSON-RPC 2.0, MCP)
+-----v------------------------------------------------------+
| dnk-mcp-creo (TypeScript, @modelcontextprotocol/sdk) |
| tools + zod schemas + policy + safe-write + audit |
+-----+------------------------------------------------------+
| versioned JSON-RPC over stdio ("__CREOBRIDGE__" frames)
+-----v------------------------------------------------------+
| creo-otk-bridge.exe (C++17, Creo Object TOOLKIT async) |
+-----+------------------------------------------------------+
|
Creo Parametric 9.0.2.0The editable Mermaid source is in
docs/assets/architecture.mmd. More detail:
docs/ARCHITECTURE.md.
Quick start
Prerequisites: Windows, PTC Creo Parametric 9.0.2.0 with Pro/TOOLKIT/OTK C++,
Visual Studio 2022 with the C++ workload, Node.js 20+, and a Creo license with
OTK feature 222 (or build with -UseNo222).
# 1) Install
npm install
# 2) Build the native bridge (auto-detects the Creo installation)
npm run build:native
# 3) Build the server
npm run build
# 4) Diagnose without Creo
npm run doctor:mock
# 5) Diagnose with Creo running
npm run doctor
# 6) Run the live integration smoke test
node scripts/integration-smoke.mjsYou do not need Creo to run the test suite:
npm testConnect a client
Copy the matching template from config/clients/ and replace
<REPO_ROOT> and <CREO_INSTALL_DIR>:
Client | Template | Typical location |
Claude Desktop | Claude Desktop config | |
Codex CLI |
| |
opencode | opencode config | |
Cursor |
|
Minimal configuration (dnk-mcp-creo.json):
{
"creo": {
"installDir": "<CREO_INSTALL_DIR>",
"connectMode": "attach"
},
"safety": {
"mode": "read-only"
},
"tools": {
"packs": ["core", "read"]
}
}Full settings and troubleshooting: docs/SETUP.md.
Tool packs
Pack | Tools | Enable with | Status |
| 7 | always on | Verified |
| 14 |
| Verified |
| 5 |
| Verified |
| 14 |
| Partial — copy-modify rollback pending |
| 14 |
| Partial — ISO release workflow pending |
| 11 |
| Partial — drafts, sweeps, mirror withheld |
Start with core and read, then add only the packs you need. See
docs/TOOLS.md for every tool, input, and output.
Safety
The default safety mode is read-only. Writes require an explicit mode change and are gated by the tool's write registration.

Path containment. Every file operation is resolved against Creo's live working directory; caller-supplied paths outside it are rejected.
Guards. Writes can require expected-old values and verify the result by readback.
Copy-modify-verify. Draft workflows keep the source model untouched and roll back on failure.
Audit. Every tool call is written to an append-only JSONL audit log.
Read docs/SAFETY.md before enabling copy or live mode. A
CAD write can change or destroy real work; use copies or version-controlled data.
Documentation
Document | Contents |
Install, configure, wire clients, troubleshoot | |
Complete tool catalog | |
Safety model and write policy | |
Components and design decisions | |
Bridge protocol reference | |
Milestones, verified scope, open questions | |
References and licensing guardrails | |
Third-party notices | |
Repository guide for AI coding agents |
Project layout
packages/server/ TypeScript MCP server (tools, transport, policy, audit, tests)
native/otk-bridge/ C++17 OTK async bridge + vendored nlohmann/json
scripts/ Build, acceptance, and development scripts
config/clients/ Client configuration templates
docs/ Architecture, protocol, tools, setup, safety, roadmap
.github/ CI, issue templates, DependabotCompatibility and limitations
Windows only. The native bridge requires Windows and the Creo SDK; CI runs the mock test suite on Windows.
Creo Parametric 9.0.2.0 is the verified target. Other 9.x/10.x builds should work once the SDK paths are confirmed.
Creo, Pro/TOOLKIT, and the OTK SDK are not included. Install and license them yourself.
Not every planned tool exists. The
modeling,drawing, andfeaturespacks are partial. Check docs/ROADMAP.md before relying on a tool.No npm package. Build from source or use a GitHub release. The bridge needs a local PTC SDK anyway.
This project is independent. It is not affiliated with, sponsored by, or endorsed by PTC Inc.
Contributing
Contributions are welcome. Read CONTRIBUTING.md first. The short version:
npm run typecheck
npm test
npm run build
npm run doctor:mockFor security issues, follow SECURITY.md and do not open a public issue. For questions and setup help, see SUPPORT.md. This project follows the Contributor Covenant.
License and attribution
Licensed under the Apache License 2.0. Third-party notices are in NOTICE and docs/ATTRIBUTION.md.
If you use, fork, or redistribute this project, keep the copyright and NOTICE files and credit the author:
DNK MCP Creo by Edward Nguyen — https://github.com/EdwardNguyen2854/dnk-mcp-creo
The project name and logo are covered by TRADEMARK.md. For citation metadata, see CITATION.cff.
PTC, Creo, Creo Parametric, Pro/ENGINEER, Pro/TOOLKIT, and Object TOOLKIT are trademarks or registered trademarks of PTC Inc. or its subsidiaries. This project is not affiliated with or endorsed by PTC.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Headless CAD engine & MCP server for 2D/3D drafting, solids, DXF/SVG export, and automation.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
Ovanek MCP: Model Context Protocol server for Ovanek platform tools; writes are dry-run by default.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables connecting MCP clients to local SolidWorks for automated 3D part creation, template generation, file export, and basic review via natural language.104MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for interacting with Creo Parametric CAD software. Enables tool calls like file_open, feature_set, and J-Link execution through a Python-based server and optional Java gateway.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for controlling a live SOLIDWORKS session through the Windows COM API, enabling native CAD operations like sketches, features, bodies, views, and exports, plus transactional plans and vectorization.11MIT
- FlicenseBqualityBmaintenanceEnables Codex to read and modify an active Creo Parametric session on Windows through a Node.js MCP service and Pro/TOOLKIT bridge, providing 60 tools for model inspection, parameters, dimensions, features, assemblies, sheet metal, STEP export, and version cleanup.6016-