Robotics MCP Server

robot_model

Create, import, export, and convert robot 3D models across Blender, Unity/VRChat/Resonite, and common formats. Handle .spz files and run custom scripts to streamline robotics model workflows.

Instructions

Robot model management portmanteau for Robotics MCP.

PORTMANTEAU PATTERN RATIONALE: Instead of creating 4 separate tools (create, import, export, convert), this tool consolidates related model operations into a single interface. This design:

Prevents tool explosion (4 tools -> 1 tool) while maintaining full functionality
Improves discoverability by grouping related operations together
Reduces cognitive load when working with robot models
Enables consistent model interface across all operations
Follows FastMCP 2.13+ best practices for feature-rich MCP servers

SUPPORTED OPERATIONS:

create: Create robot 3D model from scratch using Blender MCP
import: Import robot 3D model into Unity/VRChat/Resonite project
export: Export robot model from Unity to file format
convert: Convert robot model between formats
spz_check: Check .spz conversion tool availability
spz_convert: Convert .spz file to .ply or other format
spz_extract: Extract metadata from .spz file
spz_install: Install Unity Gaussian Splatting plugin (alternative to .spz)
execute_script: Execute custom Blender Python script (like Gemini-generated scripts)
list_scripts: List all available scripts in the repository by category
execute_repository_script: Execute a script from the repository with optional parameters

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No	Model format (used by create/import/export). - "fbx": Industry standard (recommended for robots) - "glb": Modern glTF 2.0 format - "obj": Simple mesh format - "vrm": VRM format (ONLY for humanoid robots)	fbx
`script`	No
`category`	No
`platform`	No	Target platform for import (unity/vrchat/resonite).	unity
`robot_id`	No	Virtual robot identifier (required for export).
`spz_path`	No	Path to .spz file (required for spz_* operations).
`operation`	Yes	The model operation to perform. MUST be one of: - "create": Create model (requires: robot_type, output_path) - "import": Import model (requires: robot_type, model_path) - "export": Export model (requires: robot_id) - "convert": Convert model (requires: source_path, source_format, target_format)
`dimensions`	No	Custom dimensions for create (length, width, height in meters).
`model_path`	No	Path to model file (required for import).
`robot_type`	No	Type of robot (required for create/import). Examples: "scout", "go2", "g1", "robbie", "custom"
`output_path`	No	Path for output file (required for create, optional for export/convert).
`script_name`	No
`source_path`	No	Source file path (required for convert).
`target_path`	No	Output file path (optional for convert).
`project_path`	No	Unity project path (for import).
`create_prefab`	No	Create Unity prefab after import.
`output_format`	No	Output format for spz_convert (ply, obj, glb).
`source_format`	No	Source file format (required for convert).
`target_format`	No	Target file format (required for convert).
`texture_style`	No	Texture style for create (realistic/stylized/simple).	realistic
`create_textures`	No	Create textures using gimp-mcp (for create).
`include_animations`	No	Include animations in export.
`unity_project_path`	No	Unity project path for spz_install.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedv0.2.1Aug 24, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / category

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / create_prefab / description
```
Added value: +"Create Unity prefab after import."
```

addedInput schema / properties / create_textures / description

Added value: +"Create textures using gimp-mcp (for create)."

addedInput schema / properties / dimensions / description

Added value: +"Custom dimensions for create (length, width, height in meters)."

addedInput schema / properties / format / description

Added value: +"Model format (used by create/import/export).\n- \"fbx\": Industry standard (recommended for robots)\n- \"glb\": Modern glTF 2.0 format\n- \"obj\": Simple mesh format\n- \"vrm\": VRM format (ONLY for humanoid robots)"

addedInput schema / properties / include_animations / description
```
Added value: +"Include animations in export."
```

addedInput schema / properties / model_path / description

Added value: +"Path to model file (required for import)."

addedInput schema / properties / operation / description

Added value: +"The model operation to perform. MUST be one of:\n- \"create\": Create model (requires: robot_type, output_path)\n- \"import\": Import model (requires: robot_type, model_path)\n- \"export\": Export model (requires: robot_id)\n- \"convert\": Convert model (requires: source_path, source_format, target_format)"

changedInput schema / properties / operation / enum

Previous value: -[
-  "create",
-  "import",
-  "export",
-  "convert",
-  "spz_check",
-  "spz_convert",
-  "spz_extract",
-  "spz_install"
-]New value: +[
+  "create",
+  "import",
+  "export",
+  "convert",
+  "spz_check",
+  "spz_convert",
+  "spz_extract",
+  "spz_install",
+  "execute_script",
+  "list_scripts",
+  "execute_repository_script"
+]

addedInput schema / properties / output_format / description

Added value: +"Output format for spz_convert (ply, obj, glb)."

addedInput schema / properties / output_path / description

Added value: +"Path for output file (required for create, optional for export/convert)."

addedInput schema / properties / platform / description

Added value: +"Target platform for import (unity/vrchat/resonite)."

addedInput schema / properties / project_path / description
```
Added value: +"Unity project path (for import)."
```

addedInput schema / properties / robot_id / description

Added value: +"Virtual robot identifier (required for export)."

addedInput schema / properties / robot_type / description

Added value: +"Type of robot (required for create/import).\nExamples: \"scout\", \"go2\", \"g1\", \"robbie\", \"custom\""

addedInput schema / properties / script

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / script_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / source_format / description

Added value: +"Source file format (required for convert)."

addedInput schema / properties / source_path / description

Added value: +"Source file path (required for convert)."

addedInput schema / properties / spz_path / description

Added value: +"Path to .spz file (required for spz_* operations)."

addedInput schema / properties / target_format / description

Added value: +"Target file format (required for convert)."

addedInput schema / properties / target_path / description

Added value: +"Output file path (optional for convert)."

addedInput schema / properties / texture_style / description

Added value: +"Texture style for create (realistic/stylized/simple)."

addedInput schema / properties / unity_project_path / description
```
Added value: +"Unity project path for spz_install."
```

Changed4 schema fields changedv1.0.0Jan 4, 2026

changedInput schema / properties / operation / enum

Previous value: -[
-  "create",
-  "import",
-  "export",
-  "convert"
-]New value: +[
+  "create",
+  "import",
+  "export",
+  "convert",
+  "spz_check",
+  "spz_convert",
+  "spz_extract",
+  "spz_install"
+]

addedInput schema / properties / output_format

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / spz_path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / unity_project_path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedDec 7, 2025

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden, and it does surface several significant behaviors such as using Blender MCP, installing plugins, and executing custom scripts. It does not, however, summarize the side effects of these operations, such as file writes, project modifications, or the safety implications of running arbitrary scripts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The SUPPORTED OPERATIONS list is structured and scannable, which is important for an 11-operation tool. The PORTMANTEAU PATTERN RATIONALE section is largely product-design commentary and imparts little invocation knowledge, making the overall description longer than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 23 parameters and 11 operation modes, the description gives an adequate but minimal high-level map. It should provide a per-operation parameter orientation or a stronger example, but the detailed operation enum and high schema coverage reduce the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is roughly 87%, so most parameter meaning already comes from the schema. The description adds little parameter-level value beyond mapping script/category/script_name loosely to the script-related operations, but it does not need to compensate because the schema is already detailed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly names the resource (robot models) and enumerates 11 concrete operations, so an agent can see this tool handles model create/import/export/convert/spz/script workflows. It is not vague or tautological, but it never explicitly distinguishes itself from sibling tools such as robot_control or robot_behavior, which prevents a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The operation bullets provide a usable map of what this tool can do, so an agent can infer relevant contexts such as 'import robot model' or 'convert .spz'. However, the description gives no when-not-to-use guidance, no explicit alternatives, and no direction to prefer a sibling tool for related but non-model operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.