feat(mcp): add Blender to the MCP catalog with a curated 4-tool default - #64463
Merged
Conversation
Contributor
|
alt-glitch
added
type/feature
tonydwb
reviewed
Jul 15, 2026
tonydwb
left a comment
tonydwb
left a comment
There was a problem hiding this comment.
Code Review Summary
Verdict: Approved
Feature adding Blender to the MCP catalog with curated 4-tool configuration. 123 additions, 0 deletions. Clean feature addition.
Reviewed by Hermes Agent
austinpickett
previously approved these changes
Jul 15, 2026
jquesnelle
enabled auto-merge
July 15, 2026 04:50
jquesnelle
disabled auto-merge
July 15, 2026 04:50
teknium1
enabled auto-merge (rebase)
July 15, 2026 04:52
teknium1
disabled auto-merge
July 15, 2026 04:52
| type: stdio | ||
| command: "uvx" | ||
| args: | ||
| - "blender-mcp" |
Collaborator
There was a problem hiding this comment.
should pin a specific version to avoid compromise
Adds optional-mcps/blender (ahujasid/blender-mcp, stdio via uvx). The server advertises 22 tools; 18 front optional asset services with no upstream trim mechanism, so tools.default_enabled pins the install to the core surface (scene/object info, viewport screenshot, code exec) and the rest stay opt-in through 'hermes mcp configure blender'. Manifests can now declare transport.env (static, non-secret subprocess env vars), parsed/validated in _parse_manifest and written by _build_server_config — used here to ship DISABLE_TELEMETRY=true per the no-telemetry-without-opt-in policy. Runtime already honored per-server env; manifests just couldn't declare it.
MCP catalog entries follow the same supply-chain rules as pyproject dependencies: exact version pin, and the pinned release must be at least 2 weeks old. blender-mcp 1.6.4 released 2026-06-11 (~5 weeks old, also the latest release). uvx now resolves the exact version instead of latest-at-launch.
teknium1
force-pushed
the
hermes/hermes-a4592603
branch
from
July 15, 2026 04:59
65b1f66 to
e63cce6
Compare
Contributor
|
Catalog entries now follow the same supply-chain rules as pyproject dependencies: - n8n: install.ref main -> full commit SHA 7a9ae007 (2026-05-23, branches/tags can be moved by the upstream owner; SHAs cannot) - new contract test: every shipped manifest must pin exactly — git installs need a 40-char SHA, uvx/npx-style launchers need pkg==X / pkg@X with a digit-leading version (rejects bare names, ranges, and npm dist-tags like @latest) - module docstring documents the pin policy (exact version, 2-week cooldown) unreal-engine and linear are http transports (server runs elsewhere) so there is nothing to pin at the transport layer. Verified: unpinning blender-mcp in the manifest makes the contract test fail with a named diagnostic; restoring the pin passes.
Contributor
|
teknium1
added a commit
that referenced
this pull request
Jul 15, 2026
The optional blender-mcp skill predates the blender MCP catalog entry (#64463) and taught the agent to hand-roll raw TCP JSON to the addon's socket on port 9876 from execute_code — bypassing the catalog's version pinning and install-time tool curation. Reworked to v2.0.0 as the companion skill for the catalog entry: - prerequisites now go through 'hermes mcp install blender' - interaction surface is the four curated MCP tools, not a raw socket - keeps the valuable content: addon setup, bpy recipes (materials, keyframes, render-to-file), pitfalls (timeouts, absolute paths, object mode), plus new pitfalls (xvfb headless, no-sandbox warning, remote-host path resolution) - explicit anti-pattern note: do not hand-roll TCP to 9876 - description shortened to <=60 chars per skill authoring standards alireza78a's original bpy patterns and pitfalls are preserved and credited. Docs page regenerated via generate-skill-docs.py (scoped to this skill only; unrelated generator drift left untouched).
teknium1
added a commit
that referenced
this pull request
Jul 15, 2026
…ry (#65066) The optional blender-mcp skill predates the blender MCP catalog entry (#64463) and taught the agent to hand-roll raw TCP JSON to the addon's socket on port 9876 from execute_code — bypassing the catalog's version pinning and install-time tool curation. Reworked to v2.0.0 as the companion skill for the catalog entry: - prerequisites now go through 'hermes mcp install blender' - interaction surface is the four curated MCP tools, not a raw socket - keeps the valuable content: addon setup, bpy recipes (materials, keyframes, render-to-file), pitfalls (timeouts, absolute paths, object mode), plus new pitfalls (xvfb headless, no-sandbox warning, remote-host path resolution) - explicit anti-pattern note: do not hand-roll TCP to 9876 - description shortened to <=60 chars per skill authoring standards alireza78a's original bpy patterns and pitfalls are preserved and credited. Docs page regenerated via generate-skill-docs.py (scoped to this skill only; unrelated generator drift left untouched).
This was referenced Jul 21, 2026
Gravezzz
pushed a commit
to Gravezzz/hermes-agent
that referenced
this pull request
Jul 21, 2026
…ry (NousResearch#65066) The optional blender-mcp skill predates the blender MCP catalog entry (NousResearch#64463) and taught the agent to hand-roll raw TCP JSON to the addon's socket on port 9876 from execute_code — bypassing the catalog's version pinning and install-time tool curation. Reworked to v2.0.0 as the companion skill for the catalog entry: - prerequisites now go through 'hermes mcp install blender' - interaction surface is the four curated MCP tools, not a raw socket - keeps the valuable content: addon setup, bpy recipes (materials, keyframes, render-to-file), pitfalls (timeouts, absolute paths, object mode), plus new pitfalls (xvfb headless, no-sandbox warning, remote-host path resolution) - explicit anti-pattern note: do not hand-roll TCP to 9876 - description shortened to <=60 chars per skill authoring standards alireza78a's original bpy patterns and pitfalls are preserved and credited. Docs page regenerated via generate-skill-docs.py (scoped to this skill only; unrelated generator drift left untouched).
randlee
pushed a commit
to randlee/hermes-agent
that referenced
this pull request
Aug 11, 2026
…ry (NousResearch#65066) The optional blender-mcp skill predates the blender MCP catalog entry (NousResearch#64463) and taught the agent to hand-roll raw TCP JSON to the addon's socket on port 9876 from execute_code — bypassing the catalog's version pinning and install-time tool curation. Reworked to v2.0.0 as the companion skill for the catalog entry: - prerequisites now go through 'hermes mcp install blender' - interaction surface is the four curated MCP tools, not a raw socket - keeps the valuable content: addon setup, bpy recipes (materials, keyframes, render-to-file), pitfalls (timeouts, absolute paths, object mode), plus new pitfalls (xvfb headless, no-sandbox warning, remote-host path resolution) - explicit anti-pattern note: do not hand-roll TCP to 9876 - description shortened to <=60 chars per skill authoring standards alireza78a's original bpy patterns and pitfalls are preserved and credited. Docs page regenerated via generate-skill-docs.py (scoped to this skill only; unrelated generator drift left untouched).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Blender to the MCP catalog (
hermes mcp install blender) with a 4-tool default surface, and teaches catalog manifests to declare static subprocess env vars (transport.env) — needed here to ship upstream telemetry disabled by default.Changes
optional-mcps/blender/manifest.yaml: new catalog entry for ahujasid/blender-mcp (stdio,uvx blender-mcp,auth: none).tools.default_enabledrestricts the default install to the core surface —get_scene_info,get_object_info,get_viewport_screenshot,execute_blender_code. The other 18 tools front optional third-party asset services (PolyHaven/Sketchfab/Hyper3D/Hunyuan3D) with no upstream trim mechanism; they stay unregistered unless opted into viahermes mcp configure blender. post_install covers the in-Blender addon setup, the no-blender -blimitation (Xvfb recipe included), and the code-execution security posture.hermes_cli/mcp_catalog.py: manifesttransport.env(string→string map) is now parsed, validated, and written into themcp_servers.<name>block by_build_server_config(). The runtime already honors per-serverenv(tools/mcp_tool.py); manifests just had no way to declare it. Used to setDISABLE_TELEMETRY=trueper the no-telemetry-without-opt-in policy.tests/hermes_cli/test_mcp_catalog.py: 3 new tests — env parsed + written, absent env leaves noenvkey (existing entries unaffected), malformed env rejected.Validation
tests/hermes_cli/test_mcp_catalog.py(incl. shipped-catalog parse of new entry)tests/tools/test_mcp_tool.pyofficial/prefix →_build_server_configdiscover_mcp_tools()→ registered = exactly core 4 + 4 MCP protocol tools, none of the 18 service tools leaked →get_scene_info+execute_blender_codeexecuted against a live Blender 4.5.3 through Hermes dispatchValidated against a live Blender 4.5.3 + blender-mcp session end-to-end (modeled, rendered, and exported a full asset through the server before writing the manifest).
Infographic