FreeCAD MCP Next
Related Servers
Alternatives to FreeCAD MCP Next
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for FreeCAD that enables AI assistants to create and manipulate 3D models via natural language.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to interact with FreeCAD for 3D modeling, macro development, and debugging through 150+ tools supporting multiple connection modes.221MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server that enables AI assistants to control FreeCAD for 3D modeling, FEM analysis, and more through natural language.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables automation of FreeCAD model creation, macro execution, and view management through a server-client architecture, supporting integration with external AI tools like Claude and Cursor.97MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes parametric FreeCAD operations as LLM tools, enabling natural-language-driven CAD modeling through a headless FreeCAD environment in Docker.-
- AlicenseNot gradedqualityFmaintenanceThis project provides a robust integration between AI assistants and FreeCAD CAD software using the Model Context Protocol (MCP). It allows external applications to interact with FreeCAD through a standardized interface, offering multiple connection methods and specialized tools.24MIT
TDQS
Scored across 14 tools
Most tools have clear distinct purposes (create, edit, delete, get, list, execute, run FEM). The main ambiguity is edit_object, whose description says it is used 'when create_object cannot handle object creation,' blurring the line between creating and editing. execute_code and execute_code_async are clearly differentiated by threading and GUI-safety rules.
Tool names generally follow a consistent verb_noun snake_case pattern (create_object, get_object, delete_object, reload_document, run_fem_analysis). Minor inconsistencies exist: get_parts_list uses 'get' while list_documents uses 'list' for essentially the same operation, and execute_code_async uses a suffix rather than a verb-prefix pattern.
14 tools is within the well-scoped 3-15 range and each tool addresses a distinct aspect of FreeCAD automation: document management, object CRUD, inspection, code execution, view capture, parts library access, and FEM analysis. No tools feel redundant or extraneous.
The surface covers the core lifecycle well: create_document, create/edit/delete_object, get_object(s), list_documents, and run_fem_analysis provide solid end-to-end workflows. Minor gaps exist, such as no explicit save_document or close_document tool, though reload_document implies an external-editing workflow and most gaps can be worked around via execute_code.