Plasticity MCP
Related Servers
Alternatives to Plasticity MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceGive your AI assistant the ability to inspect, measure, and compare 3D CAD models by dropping in a STEP file and asking engineering questions. Runs entirely on your machine with no cloud, no CAD license, and no setup.119 npm5MIT

gitcadofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to create and manipulate 3D CAD models using natural language via MCP, with git-based versioning and manufacturing output generation.1Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables AI agents to build, measure, verify, and correct parametric SolidWorks parts and assemblies locally via the COM API, supporting operations like sketching, extruding, modeling, dimensioning, material assignment, export, and assembly mating.MIT
- AlicenseAqualityCmaintenanceEnables AI agents and MCP clients to perform 3D asset creation and verification: exact b-rep CAD, GLB validation with embedded certificates, mesh inspection, and physics scenes, with most tools running without Blender.3645 npmMIT
- FlicenseAqualityCmaintenanceEnables local image-driven displacement of STL/OBJ meshes, STL/3MF export, and agent-driven texturing workflows without remote services.3-
- AlicenseBqualityBmaintenanceEnables host-local MCP bridging to Autodesk Fusion for agentic product-development workflows, including raytraced rendering, experimental native drawing automation, and safe Windows setup without admin privileges.98MIT
TDQS
Scored across 371 tools
There is massive functional overlap across the set: near-identical importers (plasticity_list_step_imports vs plasticity_list_cad_reference_imports), multiple fastener-group tools (inspect/check_layout/verify_load/verify_plate_bearing/distribute), and parallel DCB/ENF/MMB energy registries with read/list/match/record/import variants that are hard to distinguish in use. Individual descriptions are enormous but that verbosity does not resolve which of several similar tools to pick, and several pairs appear to do the same thing.
Almost all tools use a consistent snake_case verb_noun convention under a uniform plasticity_ prefix (create_*, list_*, measure_*, verify_*, analyze_*). Minor deviations and a few near-duplicate names (list_step_imports vs list_cad_reference_imports) slightly weaken predictability, but the pattern is largely readable and consistent.
371 tools is an extreme mismatch for any practical server scope, far beyond the 3-15 sweet spot. The surface is so large that it overwhelms selection, and much of the count is duplicated capability rather than distinct operations.
Inferred domain is CAD modeling plus FEA/strength verification plus print-process evidence, and the surface covers creation, editing, measurement, export, analysis, and immutable evidence registries very thoroughly with few obvious gaps. Coverage is arguably complete to the point of redundancy rather than deficient.