Blender MCP Addon

The Blender MCP addon is a Blender plugin that opens a local server inside Blender. A small relay process translates between the agent and the addon. Install the addon. Start its server from the Blender sidebar. Register the relay in your MCP client configuration.

What the Blender MCP addon does

The addon adds a server to Blender. The server listens on a local port and accepts commands in a structured format. Each command asks Blender to run one action, such as creating an object, assigning a material, or rendering a frame.

The addon runs its code inside Blender. It reaches the same Python interface that artists use from the scripting workspace. The agent can perform only the actions the addon exposes, so the exposed action list defines the scope of control.

Community builds differ in what they expose. Read the feature list in the README of the build you install before you grant an agent access to a production scene.

How the connection works

Three layers handle each request. Each layer answers one question.

• The Blender addon holds the scene and runs the requested action.
• The MCP relay server translates agent requests into the addon's command format.
• The MCP client hosts the agent and sends tool calls based on your prompt.

A request starts at the client. The relay forwards it to the addon over the local port. Blender runs the action and returns the result along the same path.

Set up the addon step by step

The steps below follow the common pattern for community builds. Menu names change between releases, so confirm each step against the README of your build.

• Download the addon file from the project repository.
• Open Blender preferences and install the file from disk.
• Enable the addon in the list of installed add-ons.
• Open the sidebar in the 3D viewport and start the server.
• Add the relay command to your MCP client configuration file.
• Restart the MCP client and confirm that Blender tools appear in its tool list.

If the tools do not appear, check the port number in both the addon panel and the client configuration. A mismatch is the most common cause of a silent failure.

Give your agent Blender tasks it can finish

Start with narrow tasks. A narrow task shows whether the connection works before you ask for a full scene. Good first tasks include the following.

• Inspect the scene and list every object with its position.
• Create a primitive and assign it a named color.
• Export the selected object to a file in a folder you choose.

Once these work, combine them into a short sequence. Ask the agent to build a simple scene, then check each step in the viewport.

Security and scope

The socket accepts commands from any process that can reach its port. Keep the server bound to localhost unless you have a specific reason to expose it on a network.

Blender scripts can read and write files anywhere the user account can reach. Give the agent a dedicated project folder. Save a backup of the scene before large automated edits.

Some builds include a tool that runs arbitrary Python inside Blender. Review that tool's permissions before you enable it. Treat generated code as untrusted until you read it.

When a hosted gateway fits better

A local addon suits one artist working on one machine. Teams that want the same tools across several agents often choose a hosted MCP gateway instead.

APIbase is an MCP gateway with a large and growing catalog of tools from hundreds of providers across many categories. An agent connected through the gateway can reach services beyond Blender from the same client configuration.

A gateway does not run Blender for you. The addon still runs on the machine that holds the scene. Use the gateway for the external services and the addon for the scene itself.

APIbase plans start at 0 USD and reach 29.99 USD. Check the pricing page for current terms before you commit.

Limits to plan around

Community addons track Blender releases with some delay. An addon written for one major Blender version can fail on another. Check the compatibility note before you upgrade Blender.

No public benchmark found compares Blender MCP addons on speed or reliability. Measure response times on your own scenes before you rely on an agent for time-sensitive work.

Large scenes slow each round trip. Each tool call adds latency, so an agent that makes dozens of small calls runs slower than one that sends a single scripted batch.

Live pricing — developer

Connect via MCP

$ curl -X POST https://apibase.pro/api/v1/tools/account.timeseries/call \
  -H "Content-Type: application/json" -d '{"params": {}}'

FAQ

What is the Blender MCP addon?

It is a Blender plugin that runs a local server inside Blender. An MCP client sends structured commands through a relay, and the addon runs them in the open scene.

Does the Blender MCP addon need an API key?

Many community builds need no key for the local link between the relay and Blender. A hosted gateway needs an account and a key, and the model provider used by your MCP client may need its own key.

Can an agent control Blender without an internet connection?

Yes, when the MCP client, the relay, and Blender run on the same machine. A hosted gateway requires a network connection.

Which Blender versions does the addon support?

Support depends on the build. Check the README of the addon you install, because version support changes between releases.

How much does a hosted MCP gateway cost?

APIbase plans range from 0 USD to 29.99 USD. The pricing page lists current terms.

Recommended next step

1. STEP 1/2 Connect your MCP client
2. STEP 2/2 Browse the full catalog

Related guides

• api website
• openai launches always-on ai agents
• uscis api for case status
• arcgis api for python

Published: 2026-10-30Source: live apibase.pro catalog snapshot