bes-blender-mcp

A Linux install recipe for the official Blender Lab MCP server (projects.blender.org/lab/blender_mcp), written as an executable specification.

What this is

Anthropic's announced install path for the Blender connector requires Claude Desktop, which currently ships only on macOS and Windows. The underlying components are open-source MCP and protocol-agnostic, so Linux users with CLI MCP clients (Claude Code, Llama.cpp, Cursor, Continue, etc.) are blocked by documentation, not by incompatibility.

This repository's SPEC.md is an executable specification — written so any MCP-capable coding agent or human operator can follow it end-to-end on a clean Linux host and arrive at a working MCP server registration that returns the live Blender scene.

The SPEC was validated end-to-end on Bazzite 44 (Atomic Fedora) with Claude Code 2.1.128 and Blender 5.1.0 (Flatpak) on 2026-05-05; see SPEC.md §18.4.1 for the first-execution report.

Audience

• Linux users running an MCP-capable agent (Claude Code, Llama.cpp, Cursor, Continue, others) who want the official Blender connector working today.
• Coding agents that have been given this repo as a work order — treat SPEC.md as the executable artefact.

What this is NOT

• Not a fork or vendoring of the upstream shim. The source of truth remains projects.blender.org/lab/blender_mcp.
• Not the ahujasid/blender-mcp community project. That is a separate, well-maintained pre-official effort. This SPEC's §8 and §9 are explicitly constructed to avoid silently picking it up via the entry-point name collision on PyPI.
• Not endorsed by Anthropic, the Blender Foundation, or Blender Lab. This is an unofficial install recipe authored by BES Studios.

How to use

1. Read SPEC.md §1 (Problem) through §3 (Operator Inputs).
2. Commit to values for the operator inputs in §3.1 (paths, MCP client, server name, scope) and §3.2 (host/port/install flavor, all defaulted).
3. Execute §14 (Reference Procedure) on your host, substituting your §3 values for the $NAME placeholders.
4. Verify against §15 (Test and Validation Matrix).

If you are an autonomous coding agent, treat SPEC.md as your work order. The acceptance bar is the union of the REQUIRED conformance profiles in §15.1.

Issues and contributions

Execution-time discoveries on other distros, with other MCP clients, or with future upstream versions belong in SPEC.md §17 (Open Questions) and §18.4 (Implementation Reports), and in this repo's issue tracker.

License

MIT. See LICENSE.