3D Model Context Protocol MCP Server

Provides a unified TypeScript interface for LLMs to interact with various 3D software applications.

Local serverstdioPython 16

What is the 3D Model Context Protocol MCP server?

Connect 3D Model Context Protocol to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Provides a unified TypeScript interface for LLMs to interact with various 3D software applications. The 3d model context protocol mcp server is what makes that connection.

What the server does

3D-MCP is a universal implementation of the Model Context Protocol for 3D software. It creates a unified TypeScript interface for LLMs to interact with Blender, Maya, Unreal Engine, and other 3D applications through a single coherent API.

  • 3D applications use different object models but share core concepts (meshes, materials, animations)
  • Zod schemas provide single-source-of-truth for validation, typing, and documentation
  • Strong typing catches errors at compile time rather than runtime
  • Rich metadata enables better AI understanding of domain objects
  • They map cleanly to what 3D applications need to do with entities
  • Standardized patterns reduce cognitive overhead

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Auto — generation eliminates repetitive code using createCrudOperations
  • Documentation — Self-documenting API with descriptions
  • compounded.ts — Compound modeling tools
  • Core — Base entities and operations used across all domains
  • Modeling — Mesh creation, editing, and topology operations
  • Animation — Keyframes, curves, clips, and animation control
  • Rigging — Skeletal systems, controls, and deformation
  • Rendering — Materials, lights, and render settings
  • Consistency — All entities have the same patterns for basic operations

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch 3D Model Context Protocol.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. 3D Model Context Protocol's toolset — Auto, Documentation, compounded.ts and 6 more — is a fair guide to whether it matches your workflow. It is maintained by team-plask; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
Autogeneration eliminates repetitive code using createCrudOperations
DocumentationSelf-documenting API with descriptions
compounded.tsCompound modeling tools
CoreBase entities and operations used across all domains
ModelingMesh creation, editing, and topology operations
AnimationKeyframes, curves, clips, and animation control
RiggingSkeletal systems, controls, and deformation
RenderingMaterials, lights, and render settings
ConsistencyAll entities have the same patterns for basic operations

Example prompts to try

  • Use 3D Model Context Protocol to Auto.
  • Use 3D Model Context Protocol to Documentation.
  • Use 3D Model Context Protocol to compounded.ts.

Frequently asked questions

3D MCP is a universal implementation of the Model Context Protocol that provides a unified TypeScript interface for Large Language Models (LLMs) to interact with various 3D software applications such as Blender, Maya, and Unreal Engine.