b123d-print-mcp
Related Servers
Alternatives to b123d-print-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to design, modify, and verify exact B-rep 3D CAD models by running build123d scripts on an OpenCascade kernel, with live three.js preview, collision and FDM printability checks, text-based spatial perception, user notes/sketch annotations, version history, and one-click export to OrcaSlicer.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to turn natural-language descriptions and dimensional sketches into validated, watertight 3D-printable STL files by compiling build123d scripts, inspecting meshes, and rendering deterministic multiview previews.MIT

gitcadofficial
AlicenseNot gradedqualityCmaintenanceEnables agents to create and manipulate 3D CAD models using natural language via MCP, with git-based versioning and manufacturing output generation.2Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and edit native CAD parts and assemblies, inspect saved geometry and measurements, retain revisions, run mechanism and interference checks, and export STEP/STL/GLB artifacts through MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to create and manipulate 3D models using OpenSCAD through MCP tools for code-based modeling, preview, and export.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to create 3D-printable CAD models using build123d, with tools for modeling, modification, analysis, and publishing to platforms like Thingiverse and GitHub.14Creative Commons Attribution Non Commercial No Derivatives 4.0 International
TDQS
Scored across 35 tools
Most tools have clearly distinct jobs across the design-to-print lifecycle, and descriptions explicitly separate close pairs such as check vs check_fit and build_part vs diagnose_failure. A few boundaries remain fuzzy, notably save_setup vs use_printer for configuration, compare vs before_after for reference comparison, and measure vs check_fit for fit numbers.
The dominant pattern is snake_case verb_noun, as in read_part, build_part, check_fit, save_version, and upload_reference. Some names break the pattern with single verbs/nouns such as section, export, recipe, params, check, and measure, and hardware_list reverses the verb_noun order, but the convention remains mostly readable and predictable.
At 35 tools, the surface is well above the rubric's well-scoped range and feels heavy for an agent to manage. The broad CAD/printing workflow justifies many specialized operations, but several fine-grained tools could likely be consolidated under action parameters.
The set covers an unusually complete workflow: onboarding and recipes, part authoring/editing, build and diagnosis, print checks and fit measurement, rendering/export, version history, remote transfer, reference inspection/tracing, and hardware BOMs. Minor gaps remain, such as no explicit delete/rename part operation and some workspace/file administration left implicit.