Skip to content

feat: add hermes-blender skill for 3D modeling and rendering - #10191

Closed
kshitijk4poor wants to merge 1 commit into
NousResearch:mainfrom
kshitijk4poor:skill/hermes-blender
Closed

feat: add hermes-blender skill for 3D modeling and rendering#10191
kshitijk4poor wants to merge 1 commit into
NousResearch:mainfrom
kshitijk4poor:skill/hermes-blender

Conversation

@kshitijk4poor

Copy link
Copy Markdown
Collaborator

Hermes-Blender Integration Skill

New skill for controlling a running Blender instance programmatically via the blender-mcp addon (2.2k stars, MIT licensed). Enables 3D modeling, materials, modifiers, animation, and rendering through Hermes.

Architecture

Hermes Agent -> Python socket (port 9876) -> Blender MCP Addon -> bpy Python API

The agent communicates with a running Blender instance via a TCP socket server created by the blender-mcp addon. Two methods:

  1. Direct socketblender_exec() pattern (like td_exec() in the TouchDesigner skill)
  2. MCP tools — optional, configure uvx blender-mcp in Hermes config

What's included

File Lines Contents
SKILL.md 215 Setup, architecture, blender_exec/blender_cmd patterns, workflow, commands, object types
references/pitfalls.md 150 19 pitfalls from live testing on Blender 5.1.1
references/bpy-api.md 220 Essential bpy: objects, transforms, bmesh, materials, modifiers, camera, lighting, rendering, animation, collections
references/recipes.md 270 5 complete recipes: low-poly landscape, glass sphere, procedural donut, turntable animation, render-to-file

Total: 4 files, 855 lines

Tested live on Blender 5.1.1

  • Installed addon via --python startup script (no manual GUI interaction needed)
  • Verified socket connection, scene creation, material assignment, EEVEE rendering
  • Discovered and documented Blender 5.x-specific pitfalls:

Key design decisions

  • Uses existing blender-mcp addon rather than building a custom handler — the addon is battle-tested (2.2k stars), supports PolyHaven asset integration and Hyper3D AI model generation
  • Direct socket pattern as primary communication (not MCP subprocess) — more reliable, same pattern as the TouchDesigner skill
  • Discovery-friendly — the skill documents how to query available engines, objects, and materials rather than hardcoding names that change between Blender versions

Related

@kshitijk4poor

Copy link
Copy Markdown
Collaborator Author

Closing in favor of updating the existing blender-mcp optional skill in-place with this richer content. New PR incoming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant