Remote Blender MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RBM_MODAL_APP | No | Change the default Modal App name. | |
| RBM_STATE_DIR | No | Change the location where local session records live. | ~/.local/state/remote-blender-mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Blender runs remotely on Modal. Create a session with mode=gui for live viewport control, or headless for batch work; inspect before editing, use execute_python for full bpy access, and inspect job_status until terminal. Set result in Python for structured output. Failed Python may partially change the scene. Render returns a job; use view_image on its artifact. Save and download projects before stopping. No local Blender is required.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sessionA | Start or reconnect to a project. GPU resources incur charges until stopped. |
| list_sessionsA | List locally recorded sessions. Records can include ended sandboxes. |
| session_statusC | Inspect remote worker, checkpoint and recent jobs; refresh user activity. |
| get_logsA | Read the tail of Blender's native log for errors not captured in Python stdout. |
| get_environmentB | Inspect actual Blender/Python versions, enabled add-ons, devices and GUI capabilities. |
| inspect_objectC | Inspect mesh counts, transforms, materials, modifiers, constraints, rig and animation action. |
| inspect_nodesC | Inspect shader, geometry or compositor nodes, sockets and links with pagination. |
| inspect_dependenciesC | Report packed/missing assets and resolved paths. Reports coverage limits explicitly. |
| describe_apiB | Discover installed operators or inspect real RNA property schemas, enums and defaults. |
| run_operatorA | Run an installed Blender operator with structured arguments and optional GUI context. |
| execute_pythonB | Queue arbitrary Python in persistent Blender. Full bpy and remote OS access. Assign a JSON-serializable value to result. Variables are per call; bpy scene state persists. Successful calls save a checkpoint by default. A timeout or running-job cancellation restarts Blender and loses unsaved changes. |
| inspect_sceneC | Inspect Blender version, frame and object transforms with pagination. |
| job_statusB | Read a job, including results, stdout and tracebacks. Optionally wait up to 30s. |
| cancel_jobC | Request cancellation. Running jobs restart Blender from its last checkpoint. |
| renderA | Queue a Cycles camera render. Requires a camera; GPU requires a GPU session. |
| control_viewportA | Control the live Blender GUI: select/frame objects, orbit, pan, zoom and shade. |
| viewport_screenshotA | Capture the actual Blender GUI window and return an inline image plus its artifact path. |
| view_imageA | Return a workspace PNG as inline MCP image content (maximum 10 MB). |
| save_projectC | Queue a durable checkpoint. Optional new workspace path exports a .blend for download. |
| open_projectA | Replace the live scene with an uploaded .blend; disables embedded script auto-run. Save current edits first. Successful open creates a new checkpoint. |
| list_checkpointsB | List saved revisions that can be restored, newest first. |
| restore_checkpointB | Replace the live scene with a saved revision. Save current edits first. |
| list_filesC | List up to 1000 workspace files, excluding internal state. |
| upload_fileC | Upload a local file to a new relative workspace path. Never overwrites. |
| download_fileC | Download a workspace file to a new local filename. Maximum size 5 GB. |
| stop_sessionA | Save a checkpoint and terminate compute. Project volume and revisions persist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
The tools mostly target distinct resources and actions, and the descriptions clarify overlaps. The main gray areas are the cluster of inspect_* tools (scene/object/nodes/dependencies), which are separable by description but could be mistaken for one another, and the render vs viewport_screenshot vs view_image trio, which requires reading the descriptions to keep straight.
Nearly all tools follow a snake_case verb_noun pattern (list_sessions, inspect_object, run_operator, save_project, upload_file). A few deviations exist: noun-first names like session_status and job_status, the noun_noun viewport_screenshot, and the bare verb render. Still largely readable and consistent.
26 tools is at or above the heavy threshold, but the scope is genuinely broad—sessions, jobs, multiple inspection types, execution, rendering, checkpoints, and file IO. Each tool maps to a distinct operation, yet the surface is on the large side and some inspection tools could potentially be consolidated.
Coverage is strong across the full lifecycle: session management, job control, scene/object/node inspection, arbitrary execution, rendering, checkpoints, and file transfer. Minor gaps exist—e.g., no file delete/move and no explicit checkpoint deletion—but core workflows are fully covered.