Skip to main content
Glama
mastercam-mcp

mastercam-mcp

by Praket7

Related Servers

Alternatives to mastercam-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables compatible MCP clients to inspect drawings, read units, layers, and entities, and create, edit, transform, or delete CAD objects through a local named-pipe bridge to AutoCAD 2025.
      23
      1
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables MCP-capable AI clients to connect to local ANSYS Mechanical and Workbench for read-only inspection and bounded model, material, load, mesh, solve, result, and save operations via PyMechanical/gRPC.
      27
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that enables MCP-compatible AI clients to inspect and control the currently open scene in a running Autodesk VRED Professional 2027 instance via a secure bridge, supporting read-only inspection and gated mutations like selection, visibility, transforms, and screenshots.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables safe, local Siemens NX automation through MCP, providing tools for part creation, sketching, extrusion, feature manipulation, measurement, save-as, and STEP export within a confined workspace.
      19
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to read and modify a running SolidWorks 2024 session, including BOM extraction, property editing, file renaming, and STEP/PDF export, with dry-run, apply, and save safeguards.
      MIT

    TDQS

    C2.9/5.0

    Scored across 59 tools

    Disambiguation2/5

    Multiple tools have unclear boundaries: get_machine_groups is an explicit alias of list_machine_groups, and get_machine_context, get_programming_context, get_stock, get_wcs, and get_active_part all return overlapping document context. Diagnostics are heavily duplicated across mastercam_status, mastercam_capabilities, discover_capabilities, mastercam_doctor, client_setup_check, get_version_report, get_compatibility_matrix, and list_tool_categories. Bare-verb tools like inspect, measure, and assert are near-indistinguishable without reading full schemas.

    Naming Consistency3/5

    Most tools follow a snake_case verb_noun pattern, but there are notable deviations: the mastercam_-prefixed noun-first family (mastercam_status, mastercam_doctor, mastercam_capabilities), bare imperatives (inspect, measure, assert), and noun-first queries (capture_view, estimate_cycle_time). The get_machine_groups/list_machine_groups pair also shows inconsistent verb choice for the same operation.

    Tool Count2/5

    Fifty-nine tools is far too many for a coherent surface, and a meaningful fraction are near-duplicates (aliases, redundant capability/diagnostic reporters, overlapping cycle-time and comparison analyzers). The domain is broad, but the same coverage could be delivered with far fewer, better-differentiated tools.

    Completeness4/5

    Coverage is genuinely deep: inspection, context gathering, preview/approve/apply with tokens, verification, rollback, audit history, simulation, and comparison workflows are all present. Gaps are minor rather than structural (e.g., no clear tool for creating or editing operations themselves), and the safety lifecycle is fully closed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues