A
licenseA
qualityD
maintenanceMCP server for integrating with Rodin Gen-2 API to generate 3D models from text descriptions or images.
6
MIT
x3d-mcp
by niknarra
Related Servers
Alternatives to x3d-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for AI-driven CAD operations, enabling parametric modeling, build, inspection, measurement, rendering, and diff comparison with STEP, DXF, and GLB export.MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server that gives an AI agent read and write access to a live SysML v2 model through the vendor-neutral OMG SysML v2 REST API.2-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that lets AI assistants create, edit, render, and export 3D models using OpenSCAD.4-
- AlicenseNot gradedqualityBmaintenanceAn MCP server for SideFX Houdini that enables AI assistants to interactively control, construct, inspect, and visually verify 3D procedural scenes through tools like node creation, parameter editing, viewport capture, and rendering.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that fixes, validates, and generates visual text content for AI coding assistants.MIT
TDQS
A3.9/5.0
Scored across 24 tools
Disambiguation4/5
Each tool has a distinct purpose, though there are several analysis (parse_scene, scene_stats, list_defs, semantic_check) and reference tools (node_info, search_nodes, field_type_info) that could initially seem overlapping. The detailed descriptions clarify when to use each, making misselection unlikely but not impossible.
Naming Consistency3/5
Most tools use an x3d_ prefix and a mix of verb_noun (e.g., x3d_generate_node) and noun_info (e.g., x3d_node_info) patterns, which is not fully consistent. The validate_x3d and validate_x3d_file_tool tools break the prefix convention, and x3dom_page/x3dom_starter use a different prefix, creating noticeable deviations.
Tool Count3/5
With 24 tools, the set is at the upper edge of what feels heavy, though the broad scope (validation, reference, generation, manipulation, analysis, web output, animation) helps justify the count. It is borderline but not excessive for the domain.
Completeness5/5
The tool surface covers the full lifecycle of X3D scenes: validation, reference lookup, generation, insertion, modification, extraction, deletion, moving, parsing, stats, semantic checks, web display, and animation. There are no obvious gaps for the stated purpose, making it a comprehensive toolkit.
Maintenance
ActivityInactive
ResponsivenessNo issues