PTC Creo API
No REST API for the Creo modeler; automation runs through in-process desktop toolkits (C, C++, Java, JavaScript) inside a licensed seat. TOOLKIT entitlements require specific subscription tiers. Major releases break custom code; Windchill adds REST and OSLC on the PLM side.
Frequently asked questions
PTC Creo scores C on Supergood's API Report Card. No REST API for the Creo modeler; automation runs through in-process desktop toolkits (C, C++, Java, JavaScript) inside a licensed seat. TOOLKIT entitlements require specific subscription tiers. Major releases break custom code; Windchill adds REST and OSLC on the PLM side.
PTC Creo has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
PTC Creo (Parametric Technology Corporation, Boston, MA; NASDAQ: PTC) is a 3D mechanical CAD (MCAD) suite for product design, simulation, and manufacturing.
Vertical: misc, horizontal MCAD/CAE/CAM and PLM. Not a vertical SaaS in any Supergood-named vertical. 3D parametric part and assembly modeling, history-based features (extrudes, revolves, sweeps, blends), large-assembly management of 1,000–100,000+ component products.
Medium and steady within installed base; share-losing at the edges to SOLIDWORKS and cloud-native Onshape/Fusion 360.
Data that lives in / flows through Creo + Windchill on behalf of an engineering organization: Native CAD parts and assemblies (.prt, .asm, .drw, .frm, .lay, .sec): geometry, feature/regeneration history, parameters, relations, family tables, layers, references, proprietary binary, version-locked to the Creo release that saved them.
Original Pro/ENGINEER released 1987; rebranded Creo 2010; current Creo 11 (2024) and Creo+ cloud-connected (2023+).
TOOLKIT requires a specific Creo entitlement / tier, not all subscriptions include customization support. In-process C TOOLKIT means crashes in custom code take down the user's Creo session; no sandboxing. Full sourced list under Sources below.
Common alternatives include Dassault SOLIDWORKS, Siemens NX, Siemens Solid Edge, Autodesk Inventor, Autodesk Fusion 360, Onshape (PTC). Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
PTC Creo has partial MCP support. PTC does not publish an official MCP server for Creo. Small community projects automate Creo Parametric through its J-Link and Python interfaces, but they are unofficial and cover only basic modeling operations.
Partially. MCP support for PTC Creo exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.