blender-mcp is now mcp-for-blender

TL;DR — nothing breaks. Your existing setup keeps working, and you do not need to change anything today.

The PyPI package blender-mcp has been renamed to mcp-for-blender, and this repository moved from ahujasid/blender-mcp to ahujasid/mcp-for-blender.

Do I need to do anything?

No. uvx blender-mcp still works exactly as before — blender-mcp on PyPI is now a compatibility wrapper that installs mcp-for-blender and hands off to it. Old links, old clones, and old config files all keep working.

When convenient, you can update your MCP client config to the new name:

{
  "mcpServers": {
    "blender": {
      "command": "uvx",
      "args": ["mcp-for-blender"]
    }
  }
}

New installs should use mcp-for-blender.

Why?

The new name says what this actually is: an MCP server for Blender. It also makes the project's status clearer — this is a community plugin, a third-party integration not made by Blender, and not to be confused with the official Blender Lab.

What did not change

• The import path is still blender_mcp — import blender_mcp works unchanged
• The Blender addon is unchanged, including its name in Preferences. Reinstalling will not create a duplicate addon entry
• addon.py is at the same path, so direct links to it still resolve
• Stars, forks, issues, and open PRs all carried over

What to watch for

If you hit any of these, please comment here:

• command not found: blender-mcp
• No module named blender_mcp
• Any dependency resolution error mentioning either package name

If something does go wrong, pip install blender-mcp==1.9.4 still gets you the last pre-rename release.

Details

The major version bump signals the rename — there are no breaking API changes in 2.0.0.