AnkusDrive
Related Servers
Alternatives to AnkusDrive
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform CAD operations through FreeCAD, including part conversion, 3D printing slicing, fluid simulation, and structural analysis, with a web dashboard for human interaction.33MIT
- AlicenseBqualityBmaintenanceEnables AI agents to create, inspect, validate, and modify parametric 3D models in a real FreeCAD instance through explicit MCP tools and a local bridge.142GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to safely generate parametric CAD parts (STEP/STL) using verified templates and FreeCAD, with validation and assembly support.1MIT
- AlicenseCqualityDmaintenanceAllows AI agents like Claude to create, edit, and query 3D models in FreeCAD through natural language.579MIT
- AlicenseBqualityCmaintenanceLets AI clients drive a headless FreeCAD instance to build and inspect parts, check mass and interference, run finite element analyses, and produce drawings, bills of materials and export files. Every call returns numeric results and rendered PNG views so the model can verify its own work.45MIT
- AlicenseBqualityBmaintenanceEnables coding agents to turn mechanical requirements into validated FreeCAD models with deterministic sizing from published standards, standard-part provenance, and automatic geometry validation.131Apache 2.0
TDQS
Scored across 286 tools
Most families are individually well-signposted, but at 286 tools there are repeated near-pairs an agent must disambiguate by reading long prose: fillet_edges vs partdesign_fillet, chamfer_edges vs partdesign_chamfer, shell_solid vs thickness, moldability_screen vs moldability_check vs optics_moldability_check, measure_distance vs min_clearance vs interference_check, and five overlapping catalog/designation tools. The descriptions do explain the differences (Part vs PartDesign workbench, screen vs solve), but selection depends on long-text reading rather than obvious naming.
Names are uniformly snake_case and overwhelmingly verb_noun (add_fastener, list_faces, measure_angle, verify_intent, declare_performance), with a stable family prefix convention (fem_*, cfd_*, sheet_*, optics_*, lifecycle_*, *_submit). Minor deviations exist where geometry primitives are bare verbs or nouns (pad, pocket, hole, revolve, loft, sweep, recipe, transform), which breaks the pattern slightly but stays readable.
286 tools is far beyond any reasonable single-server surface; even generously grouped (modelling, measurement, FEM, CFD, acoustics, optics, DEM, molding, sheet metal, PLM/lifecycle, recipes), the count is an extreme mismatch for one coherent toolset. An agent cannot hold this surface in working context, and many tools are niche oracles that will rarely be selected correctly.
Coverage is exhaustive across the full design lifecycle: parametric modelling, booleans/blends, measurement and inspection, assemblies with gates and lockfiles, catalog/buyability, FEM/CFD/thermal/acoustic/EM/molding/optics/DEM solvers each with analytic oracles, drawings and GD&T, cost/DFM, sheet metal, and PLM revision/lifecycle. Every operation appears to have its counterpart (create/verify/lock/export), leaving no obvious dead ends.