Renamed to mcp-for-blender. Installing this package installs it for you.
Until 2026-09-24 this record combined several servers published from one repository. The others now have records of their own: mcp-for-blender. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ahujasid-blender-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# blender-mcp is now **mcp-for-blender** This project has been renamed. `blender-mcp` is now a compatibility wrapper that installs [`mcp-for-blender`](https://pypi.org/project/mcp-for-blender/) for you. **Nothing you have today breaks.** There is no config change required. ## If you already use it Keep going. `uvx blender-mcp` continues to work exactly as before — this package depends on `mcp-for-blender` and hands off to it at startup. ## When convenient Update your MCP client config to use the new name: ```json { "mcpServers": { "blender": { "command": "uvx", "args": ["mcp-for-blender"] } } } ``` ## New installs ```bash uvx mcp-for-blender ``` ## Why the rename? The new name is clearer about what this is: an MCP server for Blender. The code, the Blender addon, and the import path (`blender_mcp`) are all unchanged. Source, issues, and documentation: **https://github.com/ahujasid/mcp-for-blender**
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.