Skip to main content
Glama
Sign In
PTC-MCP Integration Server

PTC-MCP Integration Server

by rweisssieker-xp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to PTC-MCP Integration Server

No user-submitted related servers found.

    Related Servers

    • solidworks-mcp

      keecherr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI (e.g., Claude) to control SolidWorks via natural language, automating part creation, sketching, and feature operations through the Model Context Protocol.
      1
      MIT

    • multiCAD-mcp

      aranyateixeira
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to control supported CAD applications through AI assistants using the Model Context Protocol, supporting drawing, layers, entities, blocks, files, exports, and natural-language automation.
      -

    • multiCAD-mcp

      GraceAoki574
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants such as Claude for Desktop or Cursor to control CAD applications including AutoCAD, ZWCAD, GstarCAD, and BricsCAD through the Model Context Protocol, using natural-language or direct tool calls for drawing, layers, blocks, entities, files, and data export.
      -

    • cad-mcp

      hiromitsdm
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes CAD geometry reasoning over STEP files to LLMs, allowing natural language queries about parts, assemblies, dimensions, holes, and mass properties.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly differentiated by prefix (creo_ vs windchill_), but 'export_part_as_step' and 'creo_export_step' could cause confusion for STEP export, and 'analyze_dependencies' lacks a clear domain indicator.

    Naming Consistency3/5

    Windchill and Creo tools follow consistent prefix_verb_noun patterns, but two tools ('analyze_dependencies', 'export_part_as_step') lack prefixes, and 'find_part_and_open_in_creo' is verbose and breaks the pattern.

    Tool Count5/5

    With 11 tools covering search, retrieval, export, and CAD interactions, the count is well-scoped for a Windchill-Creo integration server without being excessive or sparse.

    Completeness3/5

    The toolset covers basic retrieval and export workflows but lacks creation, update, or lifecycle operations (e.g., checkout/checkin), leaving notable gaps for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources