x3d-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@x3d-mcp create a simple X3D scene with a sphere"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
x3d-mcp
This project has been adopted by the Web3D Consortium. Development continues at Web3DConsortium/x3d_mcp, the official MCP server for X3D under the AI with X3D Special Interest Group. This repository is preserved as the origin implementation and for publication credit.
An MCP server that gives AI models the ability to validate, look up, generate, analyze, and render X3D content.
X3D (Extensible 3D Graphics) is the ISO standard (ISO/IEC 19775) for representing 3D scenes and objects in XML. The Model Context Protocol (MCP) is a standard that lets AI models call external tools. This server bridges the two: it exposes 24 tools and 4 workflow prompts that let an AI work with X3D using authoritative spec data rather than training-data guesses, produce schema-valid output, animate it, and render it in a browser.
Features
Validation -- Validate X3D content against the official X3D 4.0 XML Schema (26,000+ line XSD), catching invalid nodes, wrong attribute types, and hierarchy violations
Semantic Checks -- Catch real-world authoring bugs that XSD can't: missing geometry on shapes, empty grouping nodes, broken DEF/USE references, duplicate DEF names, ROUTEs with invalid fields or mismatched types, and missing viewpoints
Spec Lookup -- Query the full X3D Unified Object Model: 200+ concrete nodes, field types with constraints, inheritance chains, component/profile browsing, and parent-child hierarchy checking. Node and field descriptions are enriched at startup with human-readable authoring guidance — Hints and Warnings — sourced from the official X3D-Edit tooltip profile (
x3d-4.0.profile.xml)Scene Generation -- Programmatically create X3D content via the official x3d.py library (X3DPSAIL), manipulate scenes with targeted node insertion, and convert to standalone X3DOM HTML pages for browser rendering
Scene Manipulation -- Complete CRUD on existing scenes: modify field values on DEF'd nodes, remove nodes by DEF or type+index, and reparent nodes with cycle detection
Animation & Interaction -- Auto-generate full TimeSensor + Interpolator + ROUTE chains from a target DEF and field name (the correct interpolator is selected based on the field's type), validate and insert individual ROUTEs with full type/access-type checking, and look up animation reference docs
File Operations -- Parse existing X3D scenes into readable tree views, get node statistics by type and component, list all named (DEF'd) nodes, and extract specific node subtrees
Guided Workflows -- MCP prompts for common multi-step tasks: building a scene from scratch, auditing an existing file, animating a scene, and converting to X3DOM
Related MCP server: openscad-mcp
Quickstart
Prerequisites: Python 3.12+, uv
git clone <repo-url>
cd x3d-mcp
uv syncThe server uses stdio transport and is designed to be launched by an MCP client (see configuration below), not run standalone. To verify it starts correctly:
uv run python server.pyMCP Inspector
You can test the server interactively using the MCP Inspector, which is bundled with the mcp[cli] dependency:
uv run mcp dev server.pyThis opens a web UI where you can call each tool, see input schemas, and inspect responses.
MCP Client Configuration
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"x3d": {
"command": "uv",
"args": ["run", "python", "server.py"],
"cwd": "/absolute/path/to/x3d-mcp"
}
}
}Cursor
Add to .cursor/mcp.json in your project root. Use uv run --directory to point at the x3d-mcp project (this is more reliable than cwd, especially with paths containing spaces):
{
"mcpServers": {
"x3d": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/x3d-mcp", "python", "server.py"]
}
}
}Replace /absolute/path/to/x3d-mcp with the actual path to this repository. If Cursor can't find uv, use the full path (e.g., /opt/homebrew/bin/uv on macOS).
Tools
Validation
Tool | Parameters | Description |
|
| Validate an X3D XML string against the X3D 4.0 schema |
|
| Validate a |
Spec Lookup
Tool | Parameters | Description |
|
| Get full spec info for a node: fields, types, defaults, constraints, inheritance |
|
| Search nodes by name or description |
|
| List all components, or all nodes in a specific component |
| -- | List all X3D profiles with descriptions |
|
| Explain a field type (e.g. |
|
| Check if a parent-child node relationship is valid |
Scene Generation
Tool | Parameters | Description |
|
| Generate a complete, valid X3D scene template |
|
| Generate a single X3D node XML fragment |
|
| Insert a node into an existing scene |
|
| Wrap X3D content in a standalone X3DOM HTML page |
| -- | Generate a ready-to-open X3DOM page with an example scene |
File Operations
Tool | Parameters | Description |
|
| Parse and display the scene graph as an indented tree |
|
| Get statistics: node counts by type and X3D component |
|
| List all DEF'd (named) nodes with parent/children context |
|
| Extract a specific node subtree as XML |
Scene Manipulation
Tool | Parameters | Description |
|
| Update attribute values on a DEF'd node |
|
| Remove a node (and its children) by DEF or by type+index |
|
| Reparent a node to a new parent (or to |
Semantic Validation
Tool | Parameters | Description |
|
| Run authoring checks beyond XSD: shape completeness, empty groups, duplicate DEFs, broken USE refs, ROUTE validity (DEF refs + field names + access types + type matching), missing viewpoint |
Animation & Interaction
Tool | Parameters | Description |
|
| Generate a complete animation chain (TimeSensor + correct Interpolator + 2 ROUTEs) for a target field and insert it into the scene |
|
| Validate (DEF existence, field existence, accessType compatibility, type matching) and insert a ROUTE statement |
|
| Reference documentation for X3D's event-driven animation system |
Prompts
Prompt | Parameters | Description |
|
| Step-by-step guide to build an X3D scene from scratch |
|
| Guide to analyze and audit an existing X3D file (now includes semantic check step) |
| -- | Guide to convert X3D content into a browser-viewable HTML page |
|
| Step-by-step guide to add animation to an X3D scene |
Common Workflows
Build a 3D scene
1. x3d_scene_template(profile="Interchange", title="My Scene")
2. x3d_node_info("Sphere") -- check available fields
3. x3d_generate_node("Sphere", '{"radius": 2.5}') -- create geometry
4. x3d_add_node(scene_xml, node_xml) -- insert into scene
5. validate_x3d(scene_xml) -- verify against schema
6. x3dom_page(scene_xml, title="My Scene") -- render in browserAudit an existing X3D file
1. x3d_parse_scene("/path/to/model.x3d") -- see the scene graph tree
2. x3d_scene_stats("/path/to/model.x3d") -- get node counts by type/component
3. x3d_list_defs("/path/to/model.x3d") -- list all named nodes
4. validate_x3d_file_tool("/path/to/model.x3d") -- check schema compliance
5. x3d_semantic_check("/path/to/model.x3d") -- catch authoring bugs (broken ROUTEs, etc.)
6. x3d_extract_node("/path/to/model.x3d", def_name="SomeNode") -- inspect specific nodesModify and animate an existing scene
1. x3d_list_defs(scene_xml) -- find DEF names to target
2. x3d_modify_node(scene_xml, "RedMat",
'{"diffuseColor": "0 1 0"}') -- recolor a material
3. x3d_animation_info("interpolators") -- reference: which interp matches the field
4. x3d_animate(scene_xml, target_def="MyTransform",
field_name="rotation",
from_value="0 1 0 0",
to_value="0 1 0 6.283",
duration=4.0, loop=True) -- spin a transform around Y
5. x3d_semantic_check(scene_xml) -- verify ROUTEs are correctly wired
6. x3dom_page(scene_xml, title="Animated") -- render in browserExample: X3D input/output
A minimal X3D scene with a red sphere:
<?xml version="1.0" encoding="UTF-8"?>
<X3D profile="Interchange" version="4.0">
<Scene>
<Viewpoint description="Front" position="0 0 10"/>
<Shape>
<Appearance>
<Material diffuseColor="1 0 0"/>
</Appearance>
<Sphere radius="2"/>
</Shape>
</Scene>
</X3D>Key X3D patterns:
Shape = Appearance (Material + optional Texture) + Geometry (Box, Sphere, Cylinder, etc.)
Transform wraps children with translation, rotation, and scale
DEF/USE names let you define a node once and reuse it
SFColor is 3 floats in [0,1] range (e.g.,
1 0 0= red)SFRotation is axis-angle:
x y z angle_in_radians
Architecture
flowchart TD
Server["server.py\n24 MCP tools + 4 prompts"] --> Validation["src/validation.py\nxmlschema"]
Server --> SpecLookup["src/spec_lookup.py\nquery functions"]
Server --> Generation["src/generation.py\nx3d.py + lxml"]
Server --> FileOps["src/file_ops.py\nparse + analyze"]
Server --> SceneOps["src/scene_manipulation.py\nmodify / remove / move"]
Server --> Semantic["src/semantic_check.py\nauthoring checks"]
Server --> Animation["src/animation.py\nTimeSensor + Interp + ROUTE"]
SpecLookup --> X3DUOM["src/x3duom_loader.py\nin-memory index"]
FileOps --> X3DUOM
Semantic --> X3DUOM
Animation --> X3DUOM
SceneOps --> FileOps
Semantic --> FileOps
Animation --> FileOps
Validation --> XSD["spec/x3d-4.0.xsd"]
X3DUOM --> UOM["spec/X3dUnifiedObjectModel-4.0.xml"]
X3DUOM --> Tooltips["src/tooltip_loader.py\ntooltip enrichment"]
Tooltips --> Profile["wiki/x3d-4.0.profile.xml\nX3D-Edit authoring profile"]
Generation --> ValidationFile | Role |
| MCP entry point. Registers all 24 tools and 4 prompts with |
| Loads the X3D 4.0 XSD via |
| Parses the 43,000-line X3DUOM XML into in-memory dictionaries. Resolves full inheritance chains to collect all fields for any node. At load time calls |
| Parses |
| Query layer over the X3DUOM index: node info, search, component/profile listing, field type documentation, hierarchy checking with inheritance-aware type matching. |
| Constructs X3D nodes via the official x3d.py (X3DPSAIL) library, manipulates scene trees with lxml, and converts X3D XML to X3DOM-compatible HTML (lowercase tags, explicit closing tags, namespace stripping). |
| Reads and analyzes existing X3D content: scene graph tree view, statistics by type/component, DEF node listing, and node extraction. Exposes |
| Completes the CRUD cycle for X3D scenes: modify field values on DEF'd nodes, remove nodes by DEF or type+index, and reparent nodes with cycle detection. |
| Authoring-level checks beyond XSD: shape completeness, empty grouping nodes, duplicate DEFs, DEF/USE consistency, ROUTE validity (DEF refs + field names + access types + type matching), and missing viewpoints. |
| Auto-generates TimeSensor + Interpolator + ROUTE chains for animations (the correct interpolator is selected from the target field's type via X3DUOM lookup), validates and inserts individual ROUTEs, and provides reference documentation for X3D's event-driven animation system. |
| Bundled official spec files: X3D 4.0 XSD (with Web3D extension schemas) and the X3D Unified Object Model XML. |
| X3D-Edit authoring profile from the Web3D Consortium (Don Brutzman). Contains rich tooltip text for every X3D 4.0 node and attribute — used by |
Development
Install all dependencies including dev tools:
uv sync --group devRun the test suite:
uv run pytestThere are currently 171 tests across seven test files:
Test file | Count | Covers |
| 8 | Schema validation of valid/invalid documents, XSI attribute stripping, file handling, edge cases |
| 31 | X3DUOM loading, node info, search, components, profiles, field types, hierarchy checking |
| 26 | Scene templates, node generation, scene composition, X3DOM page output, HTML escaping |
| 36 | Scene parsing, statistics, DEF listing, node extraction, file path handling |
| 26 | Modify, remove, and move nodes; cycle detection; round-trip schema validation |
| 19 | Shape completeness, empty groups, duplicate DEFs, DEF/USE consistency, ROUTE validity, missing viewpoint |
| 25 | Animation chain generation for rotation/translation/color/scalar fields, ROUTE validation, animation reference docs |
Adding a New Tool
Implement the function in the appropriate
src/moduleRegister it in
server.pywith the@mcp.tool()decoratorWrite a detailed docstring -- the AI model sees this as the tool description
Add tests in the corresponding
tests/test_*.pyfile
Available Tools
24 toolsvalidate_x3dA
Validate an X3D XML string against the official X3D 4.0 schema.
Use this tool to check if X3D XML content is valid before presenting it to users
or writing it to files. Catches errors in node names, attribute types, hierarchy
violations, and other schema constraint violations.
Args:
x3d_xml: A complete X3D XML document string, including the XML declaration
and X3D root element. Example minimal document:
<?xml version="1.0" encoding="UTF-8"?>
<X3D profile="Interchange" version="4.0"
xmlns:xsd="https://www.w3.org/2001/XMLSchema-instance"
xsd:noNamespaceSchemaLocation="https://www.web3d.org/specifications/x3d-4.0.xsd">
<Scene/>
</X3D>
Inputs: x3d_xml (required). Returns: result
validate_x3d_file_toolA
Validate an X3D file on disk against the official X3D 4.0 schema.
Use this tool to check existing .x3d files for schema compliance.
Only XML-encoded X3D files (.x3d extension) are supported.
Args:
filepath: Absolute path to a .x3d file on disk.
Inputs: filepath (required). Returns: result
x3d_add_nodeA
Insert an X3D node into an existing scene.
Parses both the scene and the node XML, inserts the node at the specified
location, and returns the modified scene XML.
Args:
scene_xml: The complete X3D XML document to modify.
node_xml: The X3D node XML fragment to insert. Can be generated using
x3d_generate_node or written manually.
parent_def: Optional DEF name of the parent node. If provided, the node
is inserted as a child of the node with that DEF. If empty,
the node is added as a direct child of <Scene>.
Inputs: node_xml (required), scene_xml (required), parent_def. Returns: result
x3d_animateA
Generate a complete X3D animation chain and insert it into a scene.
Creates a TimeSensor, the appropriate Interpolator (auto-selected based
on the target field's type), and ROUTE statements to wire them together.
Inserts all nodes into the scene and returns the modified X3D document.
Args:
x3d_source: Complete X3D XML document string or file path.
target_def: DEF name of the node to animate (e.g., "MyTransform").
field_name: Field to animate. Examples:
- "rotation" → OrientationInterpolator
- "translation" → PositionInterpolator
- "diffuseColor" → ColorInterpolator
- "transparency" → ScalarInterpolator
from_value: Starting value as a space-separated string (e.g., "0 1 0 0").
to_value: Ending value as a space-separated string (e.g., "0 1 0 6.283").
duration: Animation cycle duration in seconds. Default 5.0.
loop: Whether the animation loops continuously. Default True.
Inputs: to_value (required), field_name (required), from_value (required), target_def (required), +3 more. Returns: result
x3d_animation_infoA
Explain X3D animation concepts and list available interpolators.
Provides reference documentation about X3D's event-driven animation system.
Call with no topic for a general overview.
Args:
topic: Focus area. Options:
- "interpolators": list all interpolator nodes with field mappings
- "timesensor": TimeSensor fields and outputs reference
- "routes": ROUTE syntax, rules, and patterns
- "examples": common animation code patterns
- "": general overview of the animation system
Inputs: topic. Returns: result
x3d_check_hierarchyA
Check if a parent-child node relationship is valid in X3D.
Verifies whether a child node can be placed inside a parent node
based on the X3D 4.0 specification's type constraints.
Args:
parent_node: The parent node name (e.g., Transform, Scene, Appearance).
child_node: The child node name (e.g., Shape, Material, Box).
Inputs: child_node (required), parent_node (required). Returns: result
x3d_extract_nodeA
Extract a specific node (and its children) from an X3D scene as XML.
Identify the target node by its DEF name, or by node type + index. Returns
the full XML subtree of the matched node. If both def_name and node_type
are given, def_name takes precedence.
Args:
x3d_source: Either an absolute file path to a .x3d file, or a complete
X3D XML document string.
def_name: The DEF name of the node to extract (e.g., "RedSphere").
Use x3d_list_defs to see available names.
node_type: The X3D node type to extract (e.g., "Material", "Transform").
Combined with index to select which instance.
index: 0-based index when extracting by node_type. Default 0 (first match).
Use x3d_scene_stats to see how many of each type exist.
Inputs: x3d_source (required), index, def_name, node_type. Returns: result
x3d_field_type_infoA
Explain an X3D field type or enumeration type.
Use this to understand what values a field accepts.
Args:
field_type: An X3D field type (e.g., SFVec3f, MFString, SFColor, SFRotation)
or an enumeration type from the spec (e.g., alphaModeChoices,
fogTypeChoices).
Inputs: field_type (required). Returns: result
x3d_generate_nodeA
Generate a single X3D node with specified field values.
Uses the official x3d.py library (X3DPSAIL) to construct the node,
ensuring type correctness by construction. Returns the XML fragment
for the node.
Args:
node_name: The X3D node name. Examples: Box, Sphere, Material, Transform,
Viewpoint, DirectionalLight, IndexedFaceSet, ImageTexture.
fields: JSON string of field name-value pairs. Examples:
'{"size": [2, 3, 1]}' for Box
'{"diffuseColor": [1, 0, 0], "transparency": 0.5}' for Material
'{"translation": [1, 2, 0], "rotation": [0, 1, 0, 1.57]}' for Transform
'{"radius": 2.5}' for Sphere
'{}' for defaults
Inputs: node_name (required), fields. Returns: result
x3d_list_componentsA
List X3D components, or list all nodes in a specific component.
Call with no arguments to see all available components.
Call with a component name to see all nodes in that component.
Args:
component_name: Optional component name. Examples: Geometry3D, Lighting,
Shape, Texturing, Navigation, Sound, HAnim.
Leave empty to list all components.
Inputs: component_name. Returns: result
x3d_list_defsA
List all DEF'd (named) nodes in an X3D scene.
DEF names are unique identifiers assigned to nodes in X3D, similar to
HTML id attributes. Returns each DEF name with the node type, parent,
and children for context. Use this to find targets for x3d_extract_node
or x3d_add_node.
Args:
x3d_source: Either an absolute file path to a .x3d file, or a complete
X3D XML document string.
Inputs: x3d_source (required). Returns: result
x3d_list_profilesA
List all X3D profiles with descriptions.
Profiles are capability tiers that define which components and nodes are available.
Common profiles: Core, Interchange, Interactive, Immersive, CADInterchange, Full.
Inputs: no named parameters. Returns: result
x3d_modify_nodeA
Modify field values on a DEF'd node in an X3D scene.
Finds the node by its DEF name and updates the specified attributes.
Returns the complete modified X3D XML document.
Args:
x3d_source: Complete X3D XML document string or file path.
def_name: The DEF name of the node to modify (e.g., "RedMat", "MainView").
field_changes: JSON string of field=value changes to apply.
Example: '{"diffuseColor": "0 1 0", "transparency": "0.5"}'
Values are set as XML attribute strings.
Inputs: def_name (required), x3d_source (required), field_changes (required). Returns: result
x3d_move_nodeA
Reparent a node from its current parent to a new parent in the scene graph.
Detaches the node (by DEF name) from its current location and appends it
as a child of the new parent. Detects and prevents cycles.
Args:
x3d_source: Complete X3D XML document string or file path.
def_name: DEF name of the node to move.
new_parent_def: DEF name of the new parent node. Leave empty to move
to be a direct child of <Scene>.
Inputs: def_name (required), x3d_source (required), new_parent_def. Returns: result
x3d_node_infoA
Get detailed specification info about an X3D node.
Returns the node's component, inheritance, all fields with types/defaults/constraints,
and a link to the official specification. Use this before generating X3D content
to ensure correct field names, types, and allowed values.
Args:
node_name: Exact X3D node name (case-sensitive). Examples: Box, Material,
Transform, IndexedFaceSet, Appearance, Viewpoint, DirectionalLight.
Inputs: node_name (required). Returns: result
x3dom_pageA
Wrap X3D scene content in a complete X3DOM HTML page.
Takes either a full X3D XML document or raw X3D scene nodes and produces
a standalone HTML page that renders the 3D scene in the browser using X3DOM.
X3DOM is a JavaScript framework that renders X3D content directly in web
browsers without plugins. This tool handles the HTML boilerplate, CDN includes,
and proper element structure.
Args:
x3d_content: Either a complete X3D XML document (the <Scene> content will
be extracted) or raw X3D node XML to place inside <scene>.
title: Page title shown in the browser tab and as a heading.
width: Width of the 3D viewport (CSS value, e.g., "800px", "100%").
height: Height of the 3D viewport (CSS value, e.g., "600px", "100vh").
show_stats: Show X3DOM rendering statistics overlay.
show_log: Show X3DOM log console overlay.
Inputs: x3d_content (required), title, width, height, +2 more. Returns: result
x3dom_starterA
Generate a complete starter X3DOM HTML page with an example scene.
Returns a ready-to-open HTML file with X3DOM loaded from CDN, a simple 3D scene (red cube with lighting and viewpoint), and clean styling. Save the output as an .html file and open it in any modern browser.
Inputs: no named parameters. Returns: result
x3d_parse_sceneA
Parse X3D content and display the scene graph as an indented tree.
Shows every node in the scene hierarchy with its DEF name (if any) and
key attribute values. Use this to understand the structure of an existing
X3D scene before modifying or analyzing it.
Args:
x3d_source: Either an absolute file path to a .x3d file, or a complete
X3D XML document string. The tool auto-detects which.
Inputs: x3d_source (required). Returns: result
x3d_remove_nodeA
Remove a node (and its children) from an X3D scene.
Identifies the target by DEF name, or by node_type + index. Returns
the modified X3D XML document with the node removed.
Args:
x3d_source: Complete X3D XML document string or file path.
def_name: DEF name of the node to remove. Takes precedence over node_type.
Use x3d_list_defs to see available names.
node_type: Node type to remove (e.g., "DirectionalLight", "Transform").
Combined with index to select which instance.
index: 0-based index when removing by node_type. Default 0 (first match).
Inputs: x3d_source (required), index, def_name, node_type. Returns: result
x3d_routeA
Validate and insert a ROUTE statement into an X3D scene.
ROUTEs connect event outputs to event inputs in X3D's event system.
This tool validates that both DEF names exist, field names are valid,
access types are compatible, and field types match before inserting.
Args:
x3d_source: Complete X3D XML document string or file path.
from_node: DEF name of the source node.
from_field: Output field on the source (must be outputOnly or inputOutput).
to_node: DEF name of the destination node.
to_field: Input field on the destination (must be inputOnly or inputOutput).
Inputs: to_node (required), to_field (required), from_node (required), from_field (required), +1 more. Returns: result
x3d_scene_statsA
Get statistics about an X3D scene: node counts by type and component.
Returns total node count, DEF'd vs anonymous nodes, node type breakdown,
and grouping by X3D component (Geometry3D, Lighting, Shape, etc.).
Use this for a quick overview before diving deeper.
Args:
x3d_source: Either an absolute file path to a .x3d file, or a complete
X3D XML document string.
Inputs: x3d_source (required). Returns: result
x3d_scene_templateA
Generate a minimal valid X3D scene template.
Returns a complete, valid X3D XML document with boilerplate already set up.
Use this as a starting point and modify the scene content as needed.
Args:
profile: X3D profile to use. Common choices:
- Interchange: basic geometry and appearance (recommended default)
- Interactive: adds sensors and user interaction
- Immersive: full VR-capable scenes
- Full: all X3D components
title: Optional scene title (added as metadata).
include_viewpoint: Whether to include a default Viewpoint node.
include_light: Whether to include a default DirectionalLight.
Inputs: title, profile, include_light, include_viewpoint. Returns: result
x3d_search_nodesA
Search for X3D nodes by name or description.
Use this when you don't know the exact node name. Searches both node names
and their descriptions in the X3D 4.0 spec.
Args:
query: Search term. Examples: "light", "texture", "animation", "sensor",
"geometry", "audio", "physics", "CAD".
Inputs: query (required). Returns: result
x3d_semantic_checkA
Run semantic checks on an X3D scene beyond XSD schema validation.
Detects common authoring issues that XSD cannot catch:
- Shape nodes missing geometry or appearance
- Empty grouping nodes (Transform, Group with no children)
- Duplicate DEF names
- USE referencing non-existent DEF
- ROUTE referencing invalid DEF names, fields, or mismatched types
- Missing Viewpoint
Returns a structured report of errors, warnings, and informational notes.
Args:
x3d_source: Complete X3D XML document string or file path.
Inputs: x3d_source (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
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.
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.
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.
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
Related MCP Connectors
MCP server for Wan AI video generation
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server for Qwen Image 3 AI image generation
Generate game-ready 3D models, textures, and audio from natural language, over MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for integrating with Rodin Gen-2 API to generate 3D models from text descriptions or images.6MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI assistants create, edit, render, and export 3D models using OpenSCAD.7-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that fixes, validates, and generates visual text content for AI coding assistants.MIT
- FlicenseNot gradedqualityBmaintenanceAn 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.3-