Is there a version with Telemetry completely removed?

[SewWhatFilms]

I've been waiting for a tool like this in terms of what capabilities it provides, but the Telemetry setup is completely evil as a concept and a total violation of IP sovereignty to have enabled by default. I'm doing essential work on a valuable IP covered by privacy and non-disclosure contracts. You get to spy on everything I do in Blender? You get to spy on my unreleased IP assets? You get to record my private user actions on my own private PC? You get to save and transmit screenshots of my work-in-progress to the cloud? You can remotely turn Telemetry back on after I've manually disabled it? You get to use my private data for model training and there's no way to guarantee deletion if I request it? That is completely INSANE! Has anyone else actually read this telemetry stuff and thought about the IP implications of it? There is no way I'm using this tool with any of that attached to it. Just opening a file with this tool installed would be a violation of my employment contracts. It's a massive lawsuit waiting to happen if a big company's assets were to get caught up in this because some junior programmer didn't read the fine print. The options included for turning off telemetry do not go nearly far enough. This is only usable if there is a version that completely guts every single piece of the telemetry plumbing. I'm glad I'm cautious and paranoid before I install anything.

[Dotoryman]

There does not appear to be a separate official “telemetry-free” build. The supported way to prevent telemetry from being sent is to set the environment variable on the MCP server process:

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

In the current code, that setting forces config.enabled = false. Both normal event submission and screenshot upload return before making a request when it is false. The Blender consent value cannot remotely override the environment-variable disable.

One important distinction for a strict NDA environment: this disables transmission, but it does not remove the telemetry implementation from the installed package. The collector can still initialize, create its local anonymous UUID file, and start an idle worker thread. If your policy requires the telemetry code and local artifact to be absent—not merely network-disabled—you would need an audited fork/vendor build that removes the telemetry decorators and collector. I could not find an official distribution that provides that stronger guarantee.

Current implementation:

• https://github.com/ahujasid/mcp-for-blender/blob/main/src/blender_mcp/telemetry.py
• https://github.com/ahujasid/mcp-for-blender/blob/main/src/blender_mcp/telemetry_decorator.py

For high-assurance use, I would combine the environment variable with an outbound firewall rule and verify the installed revision before allowing it near protected assets.