Skip to main content
Glama
SlncTrZ

CDT-Blender

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

CDT-Blender

Independent Blender MCP provider for the CDT engineering program (SlncTrZ provider: blender).

Fork. CDT-Blender adapts upstream seehiong/blender-mcp-bridge (MIT, © 2026 seehiong — LICENSE preserved verbatim) to the SlncTrZ ecosystem. Upstream pin: b8113ae (v0.1.3). This fork: 0.1.3+cdt.1. Full provenance in ATTRIBUTION.md.

SlncTrZ compliance: stable provider ID blender (blender.<tool> gateway namespace) · Streamable HTTP POST /mcp · fail-closed Bearer auth · read-only help / system_status / system_capabilities from runtime docs/TOOL_GUIDE.md with SHA-256 contract_hash · unauthenticated GET /healthz. Call help first — it is the running contract.

Boundary (CDT_Engineer): generic native 3D execution only. Discipline builders (architectural/MEP) are quarantined from the contract; standards interpretation and Audit Reports belong to CDT_Engineer Production Domains.

Status: B0 provider shell forked · Blender 4.x addon + bridge · Spec pin: CDT_Engineer@643019c

Repository role

This repo owns Blender-native runtime code, tests, bridge/addon behavior and provider documentation. Common architecture/contracts live in SlncTrZ/CDT_Engineer; pinned read-only snapshots are under specs/.

Related MCP server: Blender MCP Link

Completion invariant

Blender baseline requires both Modeling and Sculpting end-to-end. Primitive creation or rendering alone is not sufficient.

First objective

B0 proves the supported Blender-version/context matrix and bridge/addon lifecycle, then delivers:

  • provider identity/help/status/capabilities;

  • explicit UI/headless/context reporting;

  • file/scene info;

  • object list/get;

  • primitives/transforms;

  • real Blender integration tests.

Start here

  1. Read AGENTS.md.

  2. Read docs/INITIAL_HANDOFF.md and docs/ROADMAP.md.

  3. Read docs/SPEC_BASELINE.md plus specs/**.

  4. Research current bpy context behavior before choosing the bridge boundary.

References listed in the roadmap are MIT-licensed research inputs; adapt behavior/tests selectively rather than inheriting their public contract.

This server cannot be deployed

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Blender MCP Bridge

    MITHRAN-BALACHANDER
    A
    license
    A
    quality
    D
    maintenance
    Enables remote control of Blender via the Model Context Protocol, allowing users to execute Python scripts, query scene data, and generate 3D models from images. It provides a bridge for AI clients to interact directly with Blender's internal environment and automate 3D content creation.
    3
    6
    MIT

  • Blender MCP Link

    ENG-cpu-bit
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables interactive control of Blender for 3D scene manipulation, geometry creation, material application, and viewport rendering via natural language prompts through the Model Context Protocol.
    MIT

  • bMCP

    niewinny
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI to control Blender 3D through the Model Context Protocol, allowing Python execution, scene state queries, and automation of 3D workflows.
    5
    GPL 3.0

  • Chat with Blender

    Akerdogmus
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to control Blender 3D modeling and rendering through natural language commands via the Model Context Protocol.
    MIT