CDT-Blender
by SlncTrZ
README.md
# CDT-Blender
Independent Blender MCP provider for the CDT engineering program (SlncTrZ provider: `blender`).
> **Fork.** CDT-Blender adapts upstream
> [seehiong/blender-mcp-bridge](https://github.com/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`](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`](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/`.
## 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
Maintenance
ActivityMaintained
ResponsivenessNo issues