Skip to main content
Glama
520-YM

codex-creo-mcp

by 520-YM

Related Servers

Alternatives to codex-creo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Integrates 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.
      11
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      It enables Codex to inspect active Blockbench projects, capture viewports, make reversible draft edits, and connect geometry while preserving dimensions, groups, bounds, and Undo behavior.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server enabling Codex to inspect and edit HWPX documents, Excel spreadsheets, and QGIS QGS/QGZ projects on Windows with safety and fidelity.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI hosts to interact with a browser CAD workbench through model-neutral local stdio or authenticated remote MCP tools, supporting command discovery, design-health analysis, and scoped previews while never reading local files or taking over open sessions.
      MIT

    TDQS

    B3.4/5.0

    Scored across 60 tools

    Disambiguation2/5

    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.

    Naming Consistency4/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues