Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RBM_MODAL_APPNoChange the default Modal App name.
RBM_STATE_DIRNoChange 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_sessionA

Start or reconnect to a project. GPU resources incur charges until stopped.

First creation builds a Blender image and can take several minutes. Existing
projects restore their last checkpoint. Set restore_revision to recover an older
checkpoint at startup if the latest one is unusable; stop any active session first.
new_workspace=true creates a new independent Blender/Sandbox/Volume, even for the
same project label. Returned workspace_id can reopen that exact workspace later.
Without either option, the default project workspace is reused. Agent spawning,
scheduling and aggregation are entirely the caller's responsibility.
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.

Omit name and use query to search operators, e.g. export or mesh. Give an exact
operator (mesh.primitive_cube_add) or RNA type (Object) for its schema. No eval.
run_operatorA

Run an installed Blender operator with structured arguments and optional GUI context.

Use describe_api first. Supports modeling, modes, import/export, baking and more,
as available in this build. EXEC_DEFAULT must report FINISHED. Mutations save by
default. Prefer execute_python for custom logic, data APIs or modal UI interactions.
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.

Returns a job ID. On success view_image retrieves the PNG. The live session
serializes renders with edits. Render settings are restored after the job.
control_viewportA

Control the live Blender GUI: select/frame objects, orbit, pan, zoom and shade.

Requires a GUI session. Rotation is XYZ Euler angles in degrees; target pans
the view center. Changes persist in the live viewport. Capture with viewport_screenshot
after this job succeeds. Software graphics rendering happens remotely.
viewport_screenshotA

Capture the actual Blender GUI window and return an inline image plus its artifact path.

Requires a GUI session. This includes viewport overlays, selection and editor UI.
It is separate from a Cycles camera render. If the job is still queued, poll its ID
and retrieve the resulting artifact with view_image.
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.

Drains accepted jobs before saving; rejects new jobs while draining. A pending
save returns stopped=false and its job ID. Retry after it finishes. Setting
discard_unsaved=true terminates immediately and loses unsaved edits.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 26 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness4/5

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.