Instant Meshes

Provides automated 3D model processing via MCP including remeshing, simplification, quality analysis, and archival management for OBJ/GLB inputs.
  • python

2

GitHub Stars

python

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "lxy2109-instant-meshes-mcp": {
      "command": "python",
      "args": [
        "your_abs_dir/instant-meshes-mcp/server.py"
      ],
      "env": {
        "BLENDER_PATH": "your_blender3.6.abs_dir",
        "PYTHONUNBUFFERED": "1"
      }
    }
  }
}

You run an MCP server that exposes Instant Meshes powered 3D model processing through the MCP protocol. It automates remeshing, simplification, quality analysis, and archiving for OBJ/GLB files, while preserving textures and materials across batch and URL-based inputs.

How to use

Start the MCP service on your machine, then send requests from an MCP client to process models. You can analyze a model to get recommendations, perform automatic or targeted simplification or remeshing, and manage generated archives. All steps support local files, folders, and remote URLs, with material and texture preservation.

Key capabilities you’ll leverage through the MCP client include: automatic model processing that chooses the best operation (simplify or remesh) based on quality, quality analysis with actionable recommendations, and automated archival of results containing the processed model, textures, and logs.

How to install

Prerequisites you need installed on Windows: Python 3.8 or newer and Blender 3.6. Place Instant Meshes.exe in the project root. You may also need a working internet connection for dependencies.

Install the Python dependencies.

pip install -r requirements.txt

Configuration and usage details

Configure the MCP server to run locally with Python. The server is started from the root of the project and relies on the Instant Meshes tooling for heavy processing.

If you want to point Blender tooling at a specific Blender 3.6 installation, define the environment variable accordingly as shown in the example below.

# Example mcp.json configuration for a local stdio MCP server
{
  "mcpServers": {
    "instant_meshes_mcp": {
      "command": "python",
      "args": [
        "your_abs_dir/instant-meshes-mcp/server.py"
      ],
      "env": {
        "PYTHONUNBUFFERED": "1",
        "BLENDER_PATH": "your_blender3.6.abs_dir"
      }
    }
  }
}

How to start the MCP service

Run the main server script to start handling MCP requests.

python server.py

MCP.json configuration example

{
  "mcpServers": {
    "instant_meshes_mcp": {
      "command": "python",
      "args": [
        "your_abs_dir/instant-meshes-mcp/server.py"
      ],
      "env": {
        "PYTHONUNBUFFERED": "1",
        "BLENDER_PATH":"your_blender3.6.abs_dir"
      }
    }
  }
}

Additional sections

Configuration notes provide details for how the server locates Blender 3.6, how it preserves textures, and how it handles temporary files and logs. It is designed to run on Windows with Instant Meshes as a core processing engine and Blender 3.6 for GLB handling and texture extraction.

Security considerations include running with the least-privilege user, keeping dependencies up to date, and ensuring that input sources from URLs are trusted. Logs are timestamped to help trace processing history, and temporary files are cleaned up after processing completes.

Troubleshooting and notes

If processing fails, check the logs in the logs directory for details about the failure, including any issues with Blender detection or Instant Meshes execution. Ensure Blender 3.6 is installed and Blender executable permissions are correct.

The system automatically cleans temporary files after completion to avoid leaving residual data on disk. If an error occurs, transient files are removed as part of the cleanup process.

Tool references

  • process_model: Unified model processing for simplification and remeshing with optional archive creation and UV preservation.

  • analyze_model: Model quality analysis and diagnostic reports with recommendations.

  • manage_archives: Create, list, copy, clean, and inspect processing archives with structured storage for models, textures, logs, and metadata.

Glossary and notes

All input formats supported are OBJ and GLB, with outputs standardized to GLB while preserving materials and textures. GLB files are converted to OBJ for processing via Blender, then converted back to GLB for output.

Available tools

process_model

Unified model processing tool that supports simplification and remeshing with options to preserve UVs, boundaries, and to create an archival folder.

analyze_model

Quality analysis tool that inspects faces, topology, holes, and suggests improvements.

manage_archives

Archive management tool to list, clean, copy, and inspect processing archives containing model, textures, logs, and metadata.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational