Skip to main content
Glama
Sparrow51

Plasticity MCP

Related Servers

Alternatives to Plasticity MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables people and general-purpose AI agents to inspect, model, edit, verify, and export local 3D projects through MCP tools, including print preparation, without requiring a hosted 3D service key.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to plan, build, edit, and verify native SolidWorks parts through guarded CLI/MCP jobs with reproducible geometry evidence.
      PolyForm Noncommercial 1.0.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to execute editable-3D design programs, inspect their geometry, and replay or revise native project files through MCP tools.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables agents to drive native CAD operations in a local Plasticity session on macOS, including scene inspection, precise B-rep measurement, geometry creation and editing, import/export, and screenshots. An optional Workbench adds model review, validated dimensional feedback, and Creality Print slice-and-print preparation with explicit user confirmation.
      11
      2
      MIT

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the descriptions explicitly steer between overlapping read tools like plasticity_status, plasticity_list_bodies, and plasticity_body_info. plasticity_call overlaps with every specific operation since it can invoke registered operations, but its catalog/invoke role is clearly described.

    Naming Consistency4/5

    All tools consistently use the plasticity_ prefix and snake_case, making them predictable at a glance. However, the suffixes mix verb_noun patterns (list_bodies, capture_snapshot) with noun phrases (status, body_info, screenshot), so the convention is not fully uniform.

    Tool Count5/5

    With 11 tools, the server is well-scoped: it has dedicated tools for window connection, scene inspection, snapshot/diff workflows, recovery, screenshots, and generic operation invocation. No tool appears redundant enough to remove, and the count is in the ideal range for a focused MCP server.

    Completeness3/5

    The surface covers inspection, connection, snapshot/diff, reconciliation, screenshots, and generic operation invocation via plasticity_call. However, plasticity_capture_snapshot references plasticity_wait_for_change, which is absent from the tool set, and there are no explicit mutation or undo/redo wrappers, leaving notable gaps.