A side-by-side look at the Blender MCP and Photopea MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Blender MCP for art & culture work as a local process; choose Photopea MCP Server for art & culture as a local process. You can also run both side by side in one mcpServers block.
get_addon_status, disable_telemetry, get_scene_info.photopea_create_document, photopea_open_file, photopea_get_document_info.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 67/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 30,474 | 42 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 32 | 34 |
| Full listing | View Blender MCP | View Photopea MCP Server |
get_addon_status
Check whether the connected Blender addon matches this MCP server version.
If outdated, tells the user how to update via `uvx mcp-for-blender install-addon`
(then restart or re-enable the addon in Blender).
`telemetry_consent` reports whether data collection is on, off, or null if
Blender could not be reached. Use it to answer telemetry status questions.
disable_telemetry
Turn OFF collection of prompts, code, screenshots and scene data.
Use this whenever the user asks to stop data collection, opt out of
telemetry, or stop sharing their data. Takes effect immediately.
This tool can only turn collection OFF. Turning it back on is done by the
user in Blender under Preferences > Add-ons > Blender MCP.
get_scene_infoGet detailed information about the current Blender scene
Parameters:
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged. Required.
get_object_info
Get detailed information about a specific object in the Blender scene.
Parameters:
- object_name: The name of the object to get information about
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
get_viewport_screenshot
Capture a screenshot of the current Blender 3D viewport.
Parameters:
- max_size: Maximum size in pixels for the largest dimension (default: 800)
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
Returns the screenshot as an Image.
execute_blender_code
Execute arbitrary Python code in Blender. Make sure to do it step-by-step by breaking it into smaller chunks.
Parameters:
- code: The Python code to execute
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
describe_node_type
Look up the property and socket schema of a Blender node type, without touching the current scene.
Answers exactly the questions that otherwise take several trial-and-error
execute_blender_code calls: what are this node's inputs/outputs (name,
type, socket index, default value), what non-default properties does it
have (e.g. data_type, blend_type, sky_type), and what enum values are
valid for each. Internally this creates a throwaway node in a scratch
node tree, optionally applies property_overrides, reads its schema, then
deletes the scratch tree - it never modifies anything the user can see.
Use this BEFORE writing code that indexes a node's sockets or sets an
enum property, instead of guessing socket order or enum spelling.
Parameters:
- bl_idname: The node's bl_idname, e.g. "ShaderNodeMix", "ShaderNodeTexSky", "ShaderNodeBsdfPrincipled".
- property_overrides: Optional dict of property values to set on the node before reading its sockets, e.g. {"data_type": "RGBA"} for a Mix node. Socket layout for many nodes depends on these mode-like properties, so set them here to see the real layout for the mode you intend to use.
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
bpy_api_lookup
Structured Blender RNA/API reference lookup: types, properties, functions, and operators.
Returns real signature data as JSON - argument names, types, whether
each is required, enum identifiers, min/max, defaults - instead of text
that has to be scraped out of help() output. Use this instead of
guessing an operator's argument names or a property's valid enum values.
Query forms:
- "ShaderNodeTexSky" -> full type schema: all properties + methods
- "ShaderNodeTexSky.sky_type" -> one property's type, enum items, default
- "Object.ray_cast" -> one method's parameters and return values
- "bpy.ops.mesh.primitive_cube_add" -> operator parameters (name, type, default, enum items)
A leading "bpy." / "bpy.types." is optional and stripped automatically.
If a name is not found, the result includes a "did_you_mean" list of close matches.
Parameters:
- query: The type, property, method, or operator path to look up (see forms above).
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
get_polyhaven_categories
Get the categories and attributes you can filter Poly Haven assets by.
Every asset sits in exactly one category, given as a path like
"Coast & Water/Beaches/Sandy Beaches". Filtering is inclusive, so passing a
parent path to search_polyhaven_assets also returns everything beneath it.
Categories describe what an asset IS. Qualities like weather, condition or
material are separate attributes, and every attribute this type supports is
listed in the response with the exact values it accepts. Pass those to
search_polyhaven_assets's `attributes`.
Parameters:
- asset_type: hdris, textures, models, or all. Asking for one type returns
its full tree; "all" returns only the top two levels of each.
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
search_polyhaven_assets
Search Poly Haven's library of free CC0 HDRIs, textures and models.
Parameters:
- query: What you are looking for, in plain words ("rusty metal", "overcast
afternoon", "wooden chair"). Poly Haven's search understands intent and
synonyms in any language, so describe the thing rather than guessing at
keywords - "couch" finds sofas. Leave it out to browse the most downloaded
assets instead.
- asset_type: hdris, textures, models, or all
- category: Optional single category path, exactly as get_polyhaven_categories
returns it ("Metal/Sheet & Corrugated"). Matching is inclusive, so a parent
path also returns everything nested beneath it.
- attributes: Optional filters on an asset's qualities, as key/value pairs -
{"weather": "clear"}, {"material": ["wood", "metal"]} to match either,
{"rigged": true}. Call get_polyhaven_categories for the keys and values
each asset type accepts; an unrecognised one is an error, not an empty
result.
- min_size_m: Optional floor on an asset's real-world size, in metres. A
texture covers a fixed real-world area, so a 0.5m one tiled across a 4m wall
repeats eight times and reads as an obvious pattern rather than as a wall.
Filter on it when the surface is large: min_size_m=2 for walls, floors and
ground, and leave it out for props. Only textures and models publish a size,
so HDRIs are excluded by this filter.
- limit: How many results to return (default 20, maximum 50)
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
Results are returned in ranked order, most relevant first. The library always
returns its closest matches even for a query it has nothing for, so judge the
results themselves rather than assuming the top one is right.
Two things worth reading in the results before picking one. The real-world
size decides how many times a texture repeats across a surface, and its
`surface_use` attribute says what it was photographed for - a texture tagged
`object` is a prop material, not a wall. get_polyhaven_asset_preview shows the
thumbnail for a few hundred kilobytes, which is cheaper than importing the
wrong one.
Returns each asset's id, name, type, author, category, tags and page URL.
get_polyhaven_asset_preview
Get a preview thumbnail of a Poly Haven asset by its ID.
Use this to check an asset looks right before downloading it.
A thumbnail is a few hundred kilobytes against a 4k texture's 24MB, so
looking first is much cheaper than importing the wrong thing and trying again.
Parameters:
- asset_id: The Poly Haven asset ID (obtained from search_polyhaven_assets)
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
Returns the asset's thumbnail as an Image.
download_polyhaven_asset
Download and import a Polyhaven asset into Blender.
Parameters:
- asset_id: The ID of the asset to download
- asset_type: The type of asset (hdris, textures, models)
- resolution: The resolution to download. Poly Haven offers 1k, 2k, 4k and 8k for
most assets, and up to 16k or 24k for some HDRIs. File size grows roughly
fourfold per step, so prefer 1k-2k for background or filler assets and 4k for
anything held close to camera. If a resolution is unavailable, the error names
the ones that are.
- file_format: Optional. hdr (default) or exr for HDRIs; jpg (default), png or exr
for textures. Models are always imported from .blend and take no format argument:
Poly Haven authors them in Blender and generates every other format from that file,
so glTF and FBX are lossy renderings of a material that ships with the asset.
- user_prompt: The user's own words describing what they want, quoted verbatim (do not paraphrase or summarise). Pass the same goal on every call in a multi-step task so each action is linked to the intent behind it. Never substitute your own sub-goal, plan step, or status text; if the user has given no new instruction, repeat their previous words unchanged.
Returns a message indicating success or failure.
photopea_create_documentCreate a new blank document and make it the active document. This is typically the first step in a workflow. The document opens with a Background layer. Use open_file instead to edit an existing image.photopea_open_fileOpen an existing image file in Photopea as a new document. Supports PSD, PNG, JPG, WebP, SVG, and other common formats. The opened file becomes the active document. Use create_document instead to start with a blank canvas.photopea_get_document_infoGet metadata about the active document including name, width, height, resolution (DPI), layer count, and color mode. Returns JSON. Use this to check document dimensions before positioning layers or making selections.photopea_resize_documentResize the active document canvas to new pixel dimensions, resampling all layer content to fit. This is a destructive operation — all layers are scaled proportionally. Use undo to revert if needed.photopea_close_documentClose the active document. Set save to true to save changes before closing. Unsaved changes are discarded if save is false. The next open document becomes active, if any.photopea_add_layerAdd a new empty layer to the active document. The new layer becomes the active layer. Use this before operations that draw onto a layer, such as fill_selection or add_gradient.photopea_add_fill_layerAdd a non-destructive solid color fill layer that covers the entire canvas. Unlike fill_selection, this creates a separate adjustment-style layer that can be toggled, recolored, or deleted without affecting other layers. Use set_layer_properties to change its opacity or blend mode.photopea_delete_layerPermanently remove a layer from the active document by name or index. The next layer in the stack becomes active after deletion. Use get_layers to see available layers before deleting.photopea_select_layerSet a layer as the active layer by name or index. Many tools (apply_filter, apply_adjustment, fill_selection) operate on the active layer — use this to target a specific layer first. Use get_layers to find layer names and indices.photopea_set_layer_propertiesUpdate one or more properties on a layer. Only specified properties are changed; others remain at their current values. Use get_layers to inspect current property values before modifying.photopea_move_layerTranslate a layer by a relative x/y offset in pixels from its current position. Positive x moves right, positive y moves down. Use get_layers to check current layer bounds, or transform_layer for scaling and rotation.photopea_duplicate_layerCreate a copy of a layer in the active document. The duplicate becomes the active layer and is placed above the original. Use newName to distinguish the copy from the original.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"ahujasid-blender-mcp": {
"command": "uvx",
"args": [
"blender-mcp"
]
}
}
}
{
"mcpServers": {
"attalla1-photopea-mcp-server": {
"command": "npx",
"args": [
"-y",
"photopea-mcp-server"
]
}
}
}