CADPilot
Related Servers
Alternatives to CADPilot
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to programmatically build, analyze, and export 3D CAD geometry using FreeCAD through REST or MCP tools.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI to directly call FreeCAD for 3D modeling via the MCP protocol, providing 39 modeling tools including primitive creation, boolean operations, transformations, and export.3-
- FlicenseBqualityDmaintenanceEnables AI assistants to perform 3D modeling and CAD operations in FreeCAD, including geometry creation, boolean operations, and document management.78-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with FreeCAD for 3D modeling, macros, and debugging via MCP.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to create, edit, and export CAD models and drawings in a locally installed FreeCAD via MCP.3-
- AlicenseAqualityDmaintenanceEnables AI assistants to control FreeCAD 3D modeling software, allowing creation and manipulation of 3D objects, execution of Python code, and interaction with FreeCAD's parts library through natural language.10MIT
TDQS
Scored across 33 tools
Tools are generally targeted at distinct lifecycle stages: documents, modeling, sessions, assembly, and verification. A few complementary pairs overlap in purpose—`cad` vs `execute_code`, `assemble` vs `assembly_session`, `get_topology` vs `get_positioning_info`—but the descriptions clearly separate raw scripting from structured audited operations and one-shot from persistent assembly.
Names follow a consistent snake_case convention with a strong verb-first style (`list_documents`, `measure_geometry`, `recall_patterns`). Minor deviations exist: the unified mutation tool is simply `cad`, `operation_help` is noun-first, and `session_*` tools place the domain before the verb, but these read as intentional sub-patterns.
33 tools is well above the 25+ threshold and will consume significant context even with `operation_help` moving parameter docs out of docstrings. The session and assembly subsystems each contribute many small lifecycle tools that could plausibly be consolidated into fewer session/assembly commands with sub-actions.
The surface covers the core FreeCAD workflow: document/object inspection, structured modeling via `cad`, geometry measurement, assembly with anchors and joints, verification, plus sessions and pattern memory. Gaps like document close/delete, import/export, and pattern deletion/update are workaroundable via `execute_code` but are not first-class.