Serpentine3D MCP Server
Related Servers
Alternatives to Serpentine3D MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to Rhinoceros 3D and Grasshopper, enabling generative NURBS geometry, parametric definition solving, layer manipulation, and viewport capture.MIT
- AlicenseCqualityCmaintenanceEnables AI-driven 3D modeling, analysis, diagnostics, and Grasshopper integration within Rhino 3D through 90+ tools via the Model Context Protocol.1052MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered 3D modeling in Rhino 8 through 135+ tools for geometry, transformations, booleans, layers, materials, and more, using natural language.6MIT
- AlicenseAqualityCmaintenanceEnables AI-driven 3D modeling in Blender by providing tools to create primitives, apply modifiers and materials, set up lighting and cameras, capture viewport snapshots, export assets, inspect scenes, and execute Python commands via natural language.10MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-assisted 3D modeling and scene control in Autodesk Maya through natural language commands, supporting object creation, transformation, material application, and more.16 npm7MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Autodesk Maya through natural language for scene creation, modeling, material assignment, and object manipulation.1MIT
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose tied to a resource or action (curves, surfaces, booleans, transform, layers, measurement). The catch-all serp_command overlaps with nearly every other tool (e.g. extrude via command vs. serp_create_surface), but it is explicitly framed as an escape hatch, which mitigates confusion.
Every tool follows the same serp_<verb>_<noun>/serp_<noun> snake_case pattern (serp_create_curve, serp_boolean, serp_layers, serp_measure). Naming is fully predictable and consistent across all 15 tools.
15 tools is well within the ideal 3-15 range and each one earns its place covering a distinct modeling operation. No tool feels redundant or padded.
The surface covers the full modeling lifecycle: create (curve/surface), edit (transform, boolean), organize (select, layers), I/O (import/export), inspect (scene_info, measure, screenshot), and viewport/undo. The only noticeable gap is an explicit delete/remove-object operation, though serp_command and serp_undo partially compensate.