codex-creo-mcp
Related Servers
Alternatives to codex-creo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to inspect, measure, modify, import/export, and safely save CAD models through PTC's official VB API/COM bridge, including planning and validation for packaging and clearance workflows. Write operations are separated from read-only inspection with explicit confirmations, structured outputs, and audit logging.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to create, query, and modify native parametric features in an open Creo Parametric 10 session through the official C/C++ Toolkit, covering sketches, extrudes, revolves, holes, datum features, dimension and parameter edits, feature-tree inspection, and save/export operations.14MIT
- AlicenseBqualityDmaintenanceIntegrates PTC Windchill and Creo Parametric with LLM-based clients via the Model Context Protocol, enabling natural language interaction with PLM and CAD systems for tasks like part search, BOM retrieval, model operations, and exports.114MIT
- FlicenseNot gradedqualityBmaintenanceIt enables Codex to inspect active Blockbench projects, capture viewports, make reversible draft edits, and connect geometry while preserving dimensions, groups, bounds, and Undo behavior.-
- FlicenseNot gradedqualityBmaintenanceEnables Codex to read and modify Microsoft Project plans on Windows through live preview and apply workflows, as well as offline change-set operations when Project is closed. It supports task, resource, dependency, notes, export, and XML-to-MPP creation workflows.-
- AlicenseCqualityBmaintenanceEnables Codex to interact with and control FreeCAD 1.1.x locally through typed MCP tools, including health checks and an optional Python execution escape hatch for direct document manipulation.361MIT
TDQS
Scored across 60 tools
Several near-duplicate tool pairs exist: get_dimensions vs get_project_dimensions, display_safe_model vs display_project_model, planar_wall vs planar_wall_current, and parameter_copy vs multi_parameter_copy. Many safe-copy feature tools also share the same template with only the feature noun changed, so an agent is likely to misselect among these overlapping variants despite the detailed descriptions.
Most tools follow a clear creo_<verb>_<object> snake_case pattern, with consistent families like create_safe_*_copy and create_project_*. Deviations include creo_start_resident_and_get_basic_model, creo_export_step, and the misleading creo_set_project_working_directory, which only verifies rather than sets the directory.
60 tools is far beyond a well-scoped set and crosses the extreme threshold. Many tools are narrow one-feature variants that could be consolidated, such as separate round/chamfer/shell/draft/mirror copy tools, plus highly project-specific operations like hinge-pattern and backframe-size setters.
The surface is comprehensive for the intended Creo project workflow: reads for model/features/dimensions/geometry/mass properties, safe-copy creation for many feature types, part/sheetmetal/assembly/skeleton creation, assembly constraint insertion, dimension modification, sketch constraint tools, and STEP export. Minor gaps remain such as no general parameter read-back or component deletion, but agents can work around these.