blender-mcp-synthgen
MCP server for procedural 3D synthetic-data generation in Blender, providing 33 grounded tools for node graph authoring, scene-graph traversal, and parameter sweeps with schema verification.
README
blender-synthgen-mcp
Procedural 3D synthetic-data toolkit for Blender — grounded node schemas, a lazy scene-graph walker, and a Houdini→Blender knowledge base, delivered as a self-contained Blender addon with an MCP server built in.
Quick Install (Blender addon)
-
Download the latest
synthgen_mcp.zipfrom releases (or build it yourself — see below) -
Install in Blender: Edit → Preferences → Add-ons → Install from Disk → select the zip
-
Enable "Synthgen MCP" — first enable installs dependencies (~15s one-time)
-
Connect from your IDE:
Claude Code / Cursor / VS Code — add to your MCP config:
{"synthgen": {"url": "http://localhost:8400/sse"}}
That's it. The addon runs an SSE MCP server inside Blender on port 8400. Your IDE connects to it and gets 33 grounded tools for procedural 3D work.
N-panel controls
In the 3D viewport sidebar (N) → "Synthgen MCP" tab:
- Start/Stop — toggle the MCP server
- Copy MCP Config — copies the connection JSON to your clipboard
- Server status — shows running state and port
Change the port
Edit → Preferences → Add-ons → Synthgen MCP → Port (default 8400)
What's inside
The addon bundles:
- 33 MCP tools across 5 layers (setup, procedural authoring, graph introspection, pipeline, verification)
- Grounding data — extracted node schemas for Blender 5.2 (Geometry Nodes, Shader, Compositor)
- Main-thread executor — marshals all bpy calls safely from the MCP background thread
Tool layers
| Layer | Tools | Purpose |
|---|---|---|
| Setup | create_object, create_material, assign_material, set_parent, configure_render, import_asset, edit_mesh, add_keyframes |
Scene building blocks |
| Procedural | add_gn_modifier, add_node, link_sockets, set_node_property, set_socket_default, expose_parameter, add_driver, wire_attr_bridge, wire_compositor_pass |
Node graph authoring with grounded identifiers |
| Introspection | graph_nodes, graph_neighbors, graph_reachable, graph_impact_set, graph_attribute_trace, graph_snapshot |
Live scene-graph traversal |
| Pipeline | set_parameter, render, sweep, export_labels |
Parameter sweeps + provenance |
| Schema | schema_find, schema_show, schema_socket, schema_setting |
Query node schemas |
| Verify | verify_attribute_exists |
Runtime attribute checks |
| Escape hatch | execute_python |
Direct bpy access (ungrounded) |
Why this exists
Transport (a Blender MCP) is a commodity. The moat is version-exact grounding + a build→verify loop. LLMs hallucinate node/socket identifiers, so we extract the real schema from Blender itself and give the agent tools to query it — never trusting model memory. The same idea, one level up, becomes the scene-graph walker: a lazy, pull-based view over the live scene so the agent can traverse real relationships.
Governing principle (see knowledge/procedural_paradigm.md):
derive, don't set. Native Blender is imperative/destructive; the agent must live on the
procedural island (Geometry Nodes / shader / compositor / drivers), because you cannot sweep
a hand-edit, and sweeping a parameter space is the whole job.
Build from source
# Install dev dependencies
pip install -e ".[dev]"
# Run tests (offline — no Blender needed)
pytest
# Build the addon zip
python scripts/build_addon.py
# → dist/synthgen_mcp.zip
Development mode
For development without rebuilding the zip each time:
- Set Blender's
BLENDER_USER_SCRIPTSenvironment variable to point to theaddon/directory - Or symlink
addon/synthgen_mcp/into Blender's addons folder
The addon auto-detects whether it's running from source (adds src/ to path) or from a
built zip (uses bundled files).
Grounded against
- Blender 5.2.0 LTS — Geometry Nodes (360), Shader (118), Compositor (168) node schemas
- Houdini 22.0.368 — SOP/VOP/COP node schemas (for the crosswalks)
Regenerate for another version with the extractors in src/synthgen/extract/ (run inside
Blender / hython); drop results in data/schemas/<app-version>/.
Schema CLI (standalone)
The schema query tool works without Blender:
python -m synthgen.schema.query stats
python -m synthgen.schema.query show "Store Named Attribute"
python -m synthgen.schema.query --shader show "Attribute"
python -m synthgen.schema.query --compositor find "Cryptomatte"
Architecture
IDE (Claude Code / Cursor / VS Code)
│
│ MCP protocol over SSE HTTP
│
▼
Blender addon (synthgen_mcp)
├── SSE MCP server (background thread, port 8400)
├── Main-thread executor (bpy.app.timers queue)
├── 33 grounded tools
├── Bundled schema data
└── N-panel UI
See ROADMAP.md for project status and phase details.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。