rogue-blender-mcp
# Rogue Blender MCP
**Rogue Development** MCP bridge for Blender 5.1+ — modeling, sculpting, mesh ops, and full scene control through your AI host (Cursor, Claude Code, and compatible clients).
- Market: https://rogue-dev-studio.github.io/rogue-market-agent/
- Repo: https://github.com/rogue-dev-studio/rogue-blender-mcp
## Requirements
1. **Blender 5.1+** (5.2 recommended)
2. Blender **MCP** extension enabled, server **listening** (Preferences → Extensions → MCP → Start MCP Server)
3. [uv](https://github.com/astral-sh/uv) (`uvx` on PATH)
Default socket: `localhost:9876`.
## Install (Cursor)
```json
{
"mcpServers": {
"rogue-blender": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/rogue-dev-studio/rogue-blender-mcp.git",
"rogue-blender-mcp"
],
"env": {
"BLENDER_MCP_HOST": "localhost",
"BLENDER_MCP_PORT": "9876"
}
}
}
}
```
Or copy `cursor.mcp.fragment.json` into your project / user MCP config, then restart Cursor.
## Local editable install
```bash
pip install -e .
rogue-blender-mcp
```
## Workflow
1. Open Blender and start the MCP server in the extension preferences.
2. Restart Cursor so `rogue-blender` tools appear.
3. Ask the agent to model, sculpt, inspect, or render — including organic forms via Sculpt Mode and mesh editing via `bpy`.
## Capabilities
Through the live Blender session the agent can:
- Create and edit mesh geometry (extrude, bevel, boolean, modifiers)
- Enter sculpt workflows and apply mesh filters / remesh paths
- Manage materials, lights, cameras, and collections
- Execute precise Blender Python (`bpy` / `bmesh`) for advanced modeling
- Capture viewport / render output for iterative refine loops
## Contact
- Email: aris.hadisopiyan@gmail.com
- Studio: https://rogue-dev-studio.github.io/
## License
MIT — Rogue Development. See `LICENSE` and `NOTICE`.
TDQS
Scored across 26 tools
Most tools have clearly distinct targets: manual docs vs API docs, window vs area screenshots, object name vs data-block name, and interactive vs CLI execution. A few pairs are close, especially search_manual_docs and search_api_docs, but the names and first-line descriptions make the intended choice reasonably clear.
All tool names are snake_case and follow a predictable verb-first pattern: search_*, get_*, jump_to_*, execute_*, render_*. The get_blendfile_summary_* family and the repeated _for_cli suffix make parallel interactive/CLI tools easy to recognize.
At 26 tools, the surface is too heavy, and much of the count comes from every get_blendfile_summary_* tool having a _for_cli twin that duplicates the same logical operation. Consolidating the CLI variants into a mode parameter would make the set much tighter.
The domain is clearly Blender inspection, navigation, rendering, and documentation, and those workflows are well covered: object summaries, blend-file health checks, viewport jumps, screenshots, rendering, and doc search. The main gap is a lack of direct high-level object or file mutation tools, but execute_blender_code provides an escape hatch for arbitrary bpy operations.