菜单
Use CreNexus Blender MCP safely from Codex. Use when the user mentions Blender, .blend, scene plans, 3D objects, materials, render, viewport, Blender MCP, blender.environment_probe, blender.scene_plan, or asks Codex to inspect or extend Blender-related CreNexus MCP tools.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Work safely with CreNexus ComfyUI workflow validation, dry-run planning, workflow draft generation, and graph composition. Use when building, composing, repairing, validating, or reviewing ComfyUI API workflow JSON, ComfyUI probe output, txt2img dry-run flows, img2img/inpaint/upscale draft workflows, composed workflow graphs, or redacted ComfyUI job lifecycle summaries in this repository.
Use CreNexus CAD and AutoCAD MCP safely from Codex. Use when the user mentions CAD, AutoCAD, DXF, DWG, CAD plan JSON, engineering drawing, layer validation, AutoCAD COM, cad-mcp-autocad, or asks Codex to inspect, validate, generate, or extend CAD-related CreNexus MCP tools.
Use CreNexus Canvas from Codex. Use when the task involves opening the local realtime canvas, reading selected tldraw shapes, inserting generated images back into the canvas, debugging canvas realtime sync, or connecting visual ideation to CreNexus creative software workflows.
Use CreNexus Illustrator MCP safely from Codex. Use when the user mentions Adobe Illustrator, AI vector files, .ai, artboards, vector trace, Image Trace, SVG/PDF/PNG export, Illustrator COM, JSX, preflight, document_info, or asks Codex to inspect or extend Illustrator-related CreNexus MCP tools.
Use CreNexus Creative Software MCP from Codex. Use when the task involves configuring, running, inspecting, validating, or extending the CreNexus MCP stdio server; connecting Codex/Cursor/Claude Code to local creative software bridges; choosing safe MCP tools for Photoshop, Illustrator, ComfyUI, Blender, AutoCAD/DXF, CapCut/Jianying, or Adobe research; debugging MCP tools/list or tools/call; preparing redacted status reports; or deciding whether a request should use MCP, Computer Use, local scripts, or manual user action.
Use CreNexus Photoshop MCP safely from Codex. Use when the user mentions Photoshop, PS, PSD, layers, document info, subject cutout, camera raw, BatchPlay validation, Photoshop recipes, Photoshop COM, UXP or node proxy, or asks Codex to inspect or extend Photoshop-related CreNexus MCP tools.
基于 SOC 职业分类
| name | starbridge-blender-mcp |
| description | Use CreNexus Blender MCP safely from Codex. Use when the user mentions Blender, .blend, scene plans, 3D objects, materials, render, viewport, Blender MCP, blender.environment_probe, blender.scene_plan, or asks Codex to inspect or extend Blender-related CreNexus MCP tools. |
Prefer environment probes and dry-run scene plans before launching Blender or rendering. Treat .blend files, textures, asset libraries, render caches, and generated frames as private unless the user provides a public test asset.
Do not open private .blend files, run arbitrary Blender Python, scan asset libraries, download models, or render to tracked paths.
Read only what is needed:
docs/04-codex-blender.mdexamples/blender_bridge/examples/blender_bridge/probe.pyexamples/blender_bridge/scene_plan.pystarbridge_mcp/bridges/blender_safe_scene.pytests/test_computer_use_plans.pytests/test_tool_registry.pyIf available and the task is scene safety specific, also use .codex/skills/blender-safe-scene-skill/SKILL.md. If changing shared MCP behavior, read .codex/skills/starbridge-mcp/SKILL.md.
npm.cmd run blender:scene:plan
python examples\blender_bridge\probe.py --json
python examples\blender_bridge\scene_plan.py --json
python -m starbridge_mcp.server tools --json --safe-only
python examples\bridge_status.py --json --redact-paths --soft-exit
python scripts\security_check.py
Do not require Blender in CI. A missing Blender executable should return a structured warning, not a crash.
| Need | Preferred tool path | Boundary |
|---|---|---|
| Check Blender availability | blender.environment_probe | Read-only, no .blend open |
| Build safe scene idea | blender.scene_plan | Dry-run JSON plan only |
| Inspect real viewport | Computer Use only if user asks for GUI diagnosis | No private asset scan |
| Render | future confirmed sandbox recipe | No tracked output, no private textures |
Do not add tools that:
.blend files.blend outputsUse fixed templates, safe parameters, and sanitized evidence.
After Blender MCP changes, run:
python -m unittest discover -s tests
python scripts\starbridge_preflight.py --markdown
python scripts\security_check.py
python -m starbridge_mcp.server tools --json --safe-only
npm.cmd test
Report Blender desktop or CLI checks as local-only. CI should validate schema, dry-run plans, metadata, and safety boundaries without launching Blender.