Skip to main content
Glama
ANYLXB

solidworks-mcp-pro

by ANYLXB
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to solidworks-mcp-pro

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

    • solidworks-mcp

      yimu0824
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP bridge server for SolidWorks that enables AI assistants to control SolidWorks programmatically via COM automation.
      MIT

    • SolidworksMCP

      czuryk
      A
      license
      Not graded
      quality
      D
      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.
      3
      MIT

    • Q3DS SolidWorks MCP

      zarcherlot
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server enabling AI-driven CAD automation for SolidWorks at the feature level, converting intent into CAD-neutral IR and compiling it into concrete operations. It provides engineering-semantic tools and a deterministic compiler, bridging any MCP-capable AI client to SolidWorks via COM.
      AGPL 3.0

    • SolidPilot

      ConstructoAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI models to automate SolidWorks CAD at the feature level through MCP, including building parts from DXF/DWG drawings and reproducing existing parts via a deterministic compiler.
      1
      AGPL 3.0
    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.3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: health check, document info, creation of specific shapes, export, and review. The main overlap is between the specific creation tools and sw_create_from_spec_json, which can create the same supported types and may cause an agent to pick the wrong pathway.

    Naming Consistency4/5

    The sw_ prefix and verb_noun structure are used consistently, creating a readable pattern like sw_create_box, sw_export_active, and sw_review_active. Minor deviations exist with sw_health and sw_active_document_info, which omit a verb, but the overall convention is still predictable.

    Tool Count5/5

    Ten tools is well-scoped for a SolidWorks automation server covering health, modeling, export, and review. Each tool serves a distinct role in the workflow without unnecessary redundancy or bloat.

    Completeness4/5

    The tool surface covers the core workflow: health check, inspect active document, create common part types, export to standard formats, and review the result. Missing capabilities like opening/closing documents, editing existing models, or assembly support are notable but likely outside the intended focused scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources