MD MCP Plugin
Related Servers
Alternatives to MD MCP Plugin
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceConnects MCP-compatible AI agents to a local 3D garment design application through its Python API, enabling scene inspection, pattern and sewing operations, fabric/material management, simulation, mesh measurement, checkpoints, import/export, documentation search, and raw Python execution.42MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to interact with a local Blender desktop application through a TCP bridge for scene inspection, rendering, asset export, visual comparison, and controlled mesh operations.MIT
- AlicenseAqualityCmaintenanceEnables AI clients to control Cascadeur locally for scene and rig inspection, body and finger animation, keyframes, physics actions, camera control, PNG previews, and FBX import/export via stdio MCP.3610MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control and query Blender scenes through local MCP, allowing operations like retrieving scene information with objects and materials.-
- AlicenseCqualityBmaintenanceEnables an external MCP client to inspect and model in Blender through a local bridge, with typed operations scheduled on Blender's main thread and approval/credential checks for scene changes.171MIT
- AlicenseNot gradedqualityBmaintenanceEnables compatible AI clients to connect locally to inspect conversion reports, select meshes, provide bone maps, and assist with Blender/Unity repairs for avatar preparation and VRChat handoff.MIT
TDQS
Scored across 79 tools
Multiple families target the same underlying actions with subtly different semantics that an agent will struggle to separate: canvas_gesture vs scene_adapter_bezier_drag vs world_adapter_gizmo_drag vs world_adapter_arrow_step are all synthetic input primitives, and cloth_get_positions vs cloth_read_scene_positions vs mesh_read_scene all read vertex data. Several recovery/reconcile tools (md_recover_curve_operation, md_recover_cut_operation, cloth_recover_positions, world_gizmo_scale_recover_pair, md_reconcile_*) overlap heavily with each other and with md_operation_status. Descriptions are dense but help only marginally in deciding which near-duplicate to pick.
Everything is snake_case, but the prefix scheme is fragmented: world_adapter_, world_, scene_adapter_, rest_, rest_adapter_, md_, cloth_, cut_, cut_qt_, mesh_, canvas_. Verb placement also varies (world_adapter_inspect_3d and scene_adapter_inspect_2d put the verb first, while mesh_probe_runtime and cloth_probe_runtime put it last). Still readable, but not a predictable pattern across 79 tools.
79 tools for one MD plugin surface is far past the point where each tool earns its place. Large clusters of probe/runtime-capabilities, recover, and reconcile variants exist per sub-domain, which bloats the catalog beyond practical selection.
Coverage is broad across project lifecycle (connect/open/save copy), scene inspection, selection, mesh/vertex read-write, curve handle edit, cut, rest, and camera work, with explicit recovery paths. However it is lopsided: heavy on diagnostics and single-purpose primitives, while basic operations like pattern/curve creation or deletion and general undo/restore are absent.